-
Notifications
You must be signed in to change notification settings - Fork 13.4k
[DO NOT MERGE] build Enzyme as archive #140799
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
base: master
Are you sure you want to change the base?
Conversation
This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp. |
|
@bors try |
[DO NOT MERGE] build Enzyme as archive r? ghost try-job: dist-aarch64-apple
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@Kobzol this is the PR about which I asked you. The error shows up in all cases, no matter whether we build Enzyme and/or LLVM as static or dynamic. In https://github.com/rust-lang/rust/pull/140799/files#diff-5a1e05f2688d271039171a547d407d0c8a96715ee64d35562fc76b4c9a874303 we link against Enzyme inside of That could be checked in I think in general I'm just confused by bootstrap and how we should fix it. Bjorn or you said Backends can be dlopen'ed and thus swapped at rustc runtime. So if we link Enzyme statically, we should only do that once when building rustc for the first time. When building it dynamically we should do it every time, and thus tell rustc where to find it, even when building cranelift, right? Any suggestions on how to handle this? Preferably I would get libEnzyme.so to work (since the artifact can be re-used by downstream users), but either approach is fine to get started. I am also confused by the fact that my rust code first adds
|
r? ghost
try-job: dist-aarch64-apple