-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rustc 32bits takes one hour to compile with optimisations on #24601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Apparently some people can't reproduce. I'm on Windows 7 with |
Same with |
Cannot reproduce it with |
I think it's a 32bits vs 64bits problem. The two versions I used above are 32bits versions. |
Confirmed working with the 64bits nightly, so it's a 32bits-only problem. |
not exactly an ICE, but close enough for the tag |
For me, building glium with |
:O I admit that I only waited around 45mn. I used to compile glium with the 32bits rustc on release fairly often, and it took at most 5 minutes. |
tips: use 64-bit version rustc to compile faster :) Actually 64-bit rustc compiles about 3 times faster when bootstrapping. |
I can't use 64-bits rustc because I need to link to 32bits C libraries :( |
64-bit rustc can generate 32-bit binaries, can't it? |
This problem is still around with the 2015-07-01 nightlies. |
It is LLVM that takes 1 hour ("LLVM module passes" - try with It would be nice if you could try to compile with a cross rustc (that's a 64-bit rustc, but pass |
I was going to investigate that, and it looks like the 07-07 nightlies no longer have this problem! @arielb1 Thanks I guess :D |
EDIT: only happens with the 32bits version, 64bits version works.
Similar to #24600, but at a different step.
To reproduce: clone https://github.com/tomaka/glium/tree/aae2129a279c80a022e940393c54462b5d8df99c and run
cargo run --release
.Compiling with
opt-level=0
doesn't hang. This is withopt-level=3
.The output of
-Z time-passes
:(EDIT: I didn't wait long enough to have the rest, but it eventually works after one hour or so)
The text was updated successfully, but these errors were encountered: