Jean-Sébastien Pédron c988c24319 lang/rust: Disable "omit frame pointers" ... Before the patch, the default behavior of the compiler was to omit frame pointers. However, even though it looks fine for the code produced by the compiler, the compiler itself was broken. When there was a compilation error, rustc panics to report that error. While handling that panic, it tries to unwind the stack but fails to do so, which results in an abort(3). Here is an example: $ rustc hello.rs error: invalid reference to argument `0` (no arguments given) --> hello.rs:2:5 | 2 | println!("Hello {}") | ^^^^^^^^^^^^^^^^^^^^ | = note: this error originates in a macro outside of the current crate error: aborting due to previous error fatal runtime error: failed to initiate panic, error 5 Abort trap (core dumped) The problem also exists on other systems such as OpenBSD and i686-unknown-linux-musl. "omit frame pointers" was already disabled for i686-unknown-linux-musl: 88a28ff602/src/librustc_back/target/i686_unknown_linux_musl.rs (L22) The patch does the same for *-unknown-freebsd. See the upstream bug for more informations: https://github.com/rust-lang/rust/issues/43575		2017-11-30 13:33:05 +00:00
..
config.toml
extra-patch-ino64
old_fstat.c
patch-src_libbacktrace_fileline.c
patch-src_librustc__back_target_freebsd__base.rs	lang/rust: Disable "omit frame pointers"	2017-11-30 13:33:05 +00:00
patch-src_librustc__back_target_i686__unknown__freebsd.rs	lang/rust: avoid LLVM targeting SSE2 on i386 by default	2017-11-27 22:02:29 +00:00
patch-src_librustc__llvm_build.rs
patch-src_llvm_utils_llvm-build_llvmbuild_main.py