Björn Steinbrink a17fb64fce Workaround LLVM optimizer bug by not marking &mut pointers as noalias ... LLVM's memory dependence analysis doesn't properly account for calls that could unwind and thus effectively act as a branching point. This can lead to stores that are only visible when the call unwinds being removed, possibly leading to calls to drop() functions with b0rked memory contents. As there is no fix for this in LLVM yet and we want to keep compatibility to current LLVM versions anyways, we have to workaround this bug by omitting the noalias attribute on &mut function arguments. Benchmarks suggest that the performance loss by this change is very small. Thanks to @RalfJung for pushing me towards not removing too many noalias annotations and @alexcrichton for helping out with the test for this bug. Fixes #29485		2016-02-10 23:09:47 +01:00
..
adjustments.rs
coercions.rs
consts.rs
drop.rs	Avoid quadratic growth of functions due to cleanups	2016-02-04 00:34:53 +01:00
extern-functions.rs
fatptr.rs
function-arguments.rs	Workaround LLVM optimizer bug by not marking &mut pointers as noalias	2016-02-10 23:09:47 +01:00
gdb_debug_script_load.rs
intrinsic-no-unnamed-attr.rs
link_section.rs
loads.rs
match.rs
mir_zst_stores.rs	[MIR] Avoid some code generation for stores of ZST	2016-01-12 21:35:10 +02:00
refs.rs
stores.rs