No nightlies for several consecutive days #34572
Comments
|
Apparently a known issue. Should be fixed now? @alexcrichton |
|
Indeed still a problem. Two days' ago fix wasn't enough, and yesterday's fix also wasn't enough. Looking into the next failure. |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Jun 30, 2016
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 rust-lang#34572
bors
added a commit
that referenced
this issue
Jul 1, 2016
…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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
By the way, nice dashboard!The text was updated successfully, but these errors were encountered: