about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2016-07-01 12:51:59 -0700
committerGitHub <noreply@github.com>2016-07-01 12:51:59 -0700
commit5661be01b61bbd22afbd95fde88591bc50947b42 (patch)
tree2204eef0ec6ef6653e8d2b39ae5fee9ca5e368a3 /src/rustllvm/RustWrapper.cpp
parent16281888c0f319706cd07e3c569e0aeb5a66d3b6 (diff)
parentab06acedd650d25fcdecf1ee08bb4eb2837669bd (diff)
downloadrust-5661be01b61bbd22afbd95fde88591bc50947b42.tar.gz
rust-5661be01b61bbd22afbd95fde88591bc50947b42.zip
Auto merge of #34578 - alexcrichton:lets-just-keep-trying-to-fix-the-nightlies, r=brson
mk: Request -march=i686 on i686 Linux

Apparently the gcc on our dist bot is so old and/or obscure that the default
`-m32` switch doesn't think it can generate i686 code (or something like that).
The compiler-rt build system probes for the `__i686__` define in GCC to compile
for an i686 (vs i386) target, so this was failing on the bots.

This tweaks instead to pass `-march=i686` on i686-unknown-linux-gnu to C code to
ensure that we're compiling for i686 instead of i386. This should hopefully not
actually have an impact other than maybe doing some random optimization it
wasn't able to do so before. In theory this isn't making the target less
compatible as all Rust code is already compiled for i686.

Hopefully closes #34572
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions