Conversation
|
There was a problem hiding this comment.
The NewPM support has turned into a big mess because there were major API changes in all of the recent releases. After the LLVM 12 upgrade, we should probably look into switching to NewPM by default (as clang will be doing so soon as well), and drop support for NewPM on older LLVM versions to reduce the mess.
There was a problem hiding this comment.
-Z split-dwarf=split no longer automatically implies that debuginfo is enabled. This is in line with changes in GCC and clang (https://reviews.llvm.org/D80391), though I'm not sure what changed to affect rustc (the referenced revision only affects the frontend).
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. |
|
⌛ Trying commit 9d6d477232c745d961b5610be3e0c2c22672b901 with merge dea4d1f65a5c24b55d88ff3ce5d3c78bab1b270d... |
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
After updating the python version, the next issue is a linker error: |
|
The python3 thing will definitely need changes to the readme and possibly a relnotes tag. The |
|
Looks like using LLD as the linker instead avoids the error, so possibly it's a binutils linker bug? |
|
That builder also uses a custom binutils, so that version could be updated if needed. |
|
@cuviper Just tried that, but updating to the latest binutils version didn't help. |
|
Found similar error https://bugs.gentoo.org/760324 , solved with -fuse-ld=lld in LDFLAGS |
|
@bors try |
|
⌛ Trying commit 5b736302e6fdb2ddd3ec89fad263131d13255e70 with merge a40b38546f6f09e9b2a6592ef391c84f74ab536d... |
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
@bors try |
|
⌛ Trying commit 157e1062795b17758c9174c3925d366dc5e69199 with merge be3777f1a4bdb0417cca87d7c31d9fa85596bbad... |
|
Yes, it does. |
This implements the necessary adjustments to make rustc work with LLVM 12. I didn't encounter any major issues so far.
r? @cuviper