-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
LLVM shouldn't be build with --disable-threads
#7071
Comments
@catamorphism, I just opened a pull request (#7393) to actually stop passing this option to configuring LLVM. The problem is that this doesn't trigger an LLVM rebuild, so once the change has gone through the bots need to have their llvm checkout cleaned before landing the further improvements (uncommenting that block of code to enable a threadsafe rustc) |
Unfortunately, the main test for this is ignored due to rust-lang#7071. Closes rust-lang#5682
We can try running the bots with |
Unfortunately, the main test for this is ignored due to rust-lang#7071. Closes rust-lang#5682
…j,xFrednet Don't lint `vec_init_then_push` when further extended fixes rust-lang#7071 This will still lint when a larger number of pushes are done (four currently). The exact number could be debated, but this is more readable then a sequence of pushes so it shouldn't be too large. changelog: Don't lint `vec_init_then_push` when further extended. changelog: Remove `mut` binding from `vec_init_then_push` when possible.
After #6511 and #7040, rustc is ready to use LLVM completely threadsafely.
All that's missing is to stop passing the
--disable-threads
and--disable-pthreads
flags to LLVM's configure script. Once this is done, the lock-enabling code in trans should be uncommented as well.This is a simple change, but requires the bots to rebuild LLVM (which has caused problems in the past). @brson has some other LLVM patches to integrate, and this would fit nicely with those.
The text was updated successfully, but these errors were encountered: