-
Notifications
You must be signed in to change notification settings - Fork 13.6k
bootstrap: x.py dist rustc-src
should keep LLVM's siphash
#145121
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
bootstrap: x.py dist rustc-src
should keep LLVM's siphash
#145121
Conversation
This comment has been minimized.
This comment has been minimized.
4e6df5a
to
d078184
Compare
This comment has been minimized.
This comment has been minimized.
d078184
to
a27a7ec
Compare
This comment has been minimized.
This comment has been minimized.
a27a7ec
to
f208a45
Compare
This comment has been minimized.
This comment has been minimized.
f208a45
to
f05b20a
Compare
f05b20a
to
cba5918
Compare
Thanks for taking a look! I think that something like this makes sense, yeah. I wonder why r? @Kobzol |
@Kobzol rust/src/bootstrap/src/core/build_steps/dist.rs Line 1061 in 2886b36
|
does |
Right, the naming confused me yet again, sorry. Hmm, then that's weird, as |
|
So here's a suspicious thing that happens when I do
we're in the Here's my bootstrap.toml
(and I also modify distcheck not to pass |
Yeah you can see the same thing on CI for example this build the raw log has this:
we're in the |
Ok, it's happening because distcheck just invokes when the inner bootstrap runs, it calls rust/src/bootstrap/src/core/config/config.rs Lines 473 to 475 in ffb9d94
And I tried a naive change to add rust/src/bootstrap/mk/Makefile.in Line 16 in ffb9d94
but then
Which makes sense because we specifically exclude And at this point I'm stuck. I can't tell if there's some way to configure tidy not to do the gcc_submodule check or maybe the plain tarball should include some breadcrumb that the tidy check could look for Update yeah if i comment out the tidy gcc_submodule check, and pass
Update2: @Kobzol I went ahead and added the distcheck fix here too:
Does that sound right? I am not sure if passing |
b9676c2
to
ea85921
Compare
Thanks a lot for investigating this! ❤️ It seems like Let's avoid any changes to distcheck and tidy in this PR, and just fix the LLVM build. |
ea85921
to
cba5918
Compare
@Kobzol I'm somewhat unhappy with all the |
It's called for every path, so I imagine it might be hot, yeah. But probably there's a much better way of implementing this.. Anyway, we can resolve that in a separate PR. Thank you for investigating this! I can't reproduce the original issue on Linux, but the directory is now there in the archive, so hopefully it should help on macOS. @bors r+ rollup |
Rollup of 7 pull requests Successful merges: - #144553 (Rehome 32 `tests/ui/issues/` tests to other subdirectories under `tests/ui/`) - #145064 (Add regression test for `saturating_sub` bounds check issue) - #145121 (bootstrap: `x.py dist rustc-src` should keep LLVM's siphash) - #145150 (Replace unsafe `security_attributes` function with safe `inherit_handle` alternative) - #145152 (Use `eq_ignore_ascii_case` to avoid heap alloc in `detect_confuse_type`) - #145200 (mbe: Fix typo in attribute tracing) - #145222 (Fix typo with paren rustc_llvm/build.rs) r? `@ghost` `@rustbot` modify labels: rollup
Fixes #145117