-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Inject the compiler_builtins
crate whenever the core
crate is injected
#49503
Conversation
Your PR failed on Travis. Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
If this was not helpful or you have suggestes for improvements, please ping or otherwise contact |
6c575fd
to
1a8fb17
Compare
Your PR failed on Travis. Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Your PR failed on Travis. Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
I want to point out that this PR will break some nightly users of Xargo. If they were developing a no-std library and didn't have a Xargo.toml that specified the compiler-builtins crate as part of the sysroot that Xargo will build then [dependencies.core] # add this section if you didn't have it already
stage = 0
[dependencies.compiler_builtins] # add this section
features = ["mem"] # not really required
stage = 1 @alexcrichton how do you feel about this nightly-only breaking change and the Cargo.toml modifications in the diff? This PR looks good to me but I'll leave @alexcrichton do the sign off. |
65e1c99
to
88ecd6c
Compare
Your PR failed on Travis. Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@TimNN I love the bot. The only slightly confusing situation is that it will post even after a commit that fails has been force pushed over with a commit that succeeds |
r=me on the rustc changes! |
@bors r=alexcrichton |
📌 Commit 247bdb9 has been approved by |
🔒 Merge conflict |
247bdb9
to
4ecbfbb
Compare
rebased @bors r=alexcrichton |
📌 Commit 4ecbfbb has been approved by |
☔ The latest upstream changes (presumably #49154) made this pull request unmergeable. Please resolve the merge conflicts. |
Fixed the merge conflict and two more Cargo.tomls; still testing locally. The Cargo.lock will need to be updated as well but that's hard to do from GH :-). |
Your PR failed on Travis. Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
I ran x.py dist for x86_64-linux and wasm32 with profilers and sanitizers enabled and it finished successfully. @oli-obk could you update the lockfile? |
3301ad2
to
679657b
Compare
@bors r=alexcrichton |
📌 Commit 679657b has been approved by |
…ins, r=alexcrichton Inject the `compiler_builtins` crate whenever the `core` crate is injected
Rollup of 9 pull requests Successful merges: - #49510 (Fix anchor position on fields) - #49652 (Fix anchors issue when everything is collapsed) - #49702 (std: Inline some Termination-related methods) - #49728 (add emit_debug_gdb_scripts target option and ..) - #49731 (add THUMB targets to rustup manifest) - #49742 (Using X headings instead of 0.X #49739) - #49748 (proc_macro: Improve Debug representations) - #49750 (bootstrap: Remove the fast path) - #49503 (Inject the `compiler_builtins` crate whenever the `core` crate is injected) Failed merges:
The compiler_builtins crate is injected automatically now: rust-lang/rust#49503
The compiler_builtins crate is injected automatically now: rust-lang/rust#49503
…sdreavus rustdoc: mask `compiler_builtins` docs Fixes rust-lang#46783. I wasn't able to fully confirm the underlying cause, but my theory is that functions in `compiler_builtins` were overwriting functions with the same names in libcore in the search index. Since the functions in `compiler_builtins` didn't have docs, that's why they weren't appearing in the results. Masking the `compiler_builtins` crate fixes the search results. It appears that this crate was accidentally unmasked in rust-lang#49503.
…sdreavus rustdoc: mask `compiler_builtins` docs Fixes rust-lang#46783. I wasn't able to fully confirm the underlying cause, but my theory is that functions in `compiler_builtins` were overwriting functions with the same names in libcore in the search index. Since the functions in `compiler_builtins` didn't have docs, that's why they weren't appearing in the results. Masking the `compiler_builtins` crate fixes the search results. It appears that this crate was accidentally unmasked in rust-lang#49503.
It depends on libcore for providing all lang items that are necessary for doing anything useful, so core can't depend on it.
r? @japaric
cc @aturon