Skip to content

Inject compiler_builtins during postprocessing and ensure it is made private#135501

Merged
bors merged 7 commits intorust-lang:masterfrom
tgross35:stdlib-dependencies-private
Feb 23, 2025
Merged

Inject compiler_builtins during postprocessing and ensure it is made private#135501
bors merged 7 commits intorust-lang:masterfrom
tgross35:stdlib-dependencies-private

Conversation

@tgross35
Copy link
Contributor

@tgross35 tgross35 commented Jan 14, 2025

Follow up of #135278

Do the following:

  • Inject compiler_builtins during postprocessing, rather than injecting extern crate compiler_builtins as _ into the AST
  • Do not make dependencies of std private by default (this was added in Exclude dependencies of std for diagnostics #135278)
  • Make sure sysroot crates correctly mark their dependencies private/public
  • Ensure that marking a dependency private makes its dependents private by default as well, unless otherwise specified
  • Do the compiler_builtins update that has been blocked on this

There is more detail in the commit messages. This includes the changes I was working on in #136226.

try-job: test-various
try-job: x86_64-msvc-1
try-job: x86_64-msvc-2
try-job: i686-mingw-1
try-job: i686-mingw-2

r? @bjorn3

@rustbot

This comment was marked as outdated.

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Jan 14, 2025
@tgross35 tgross35 marked this pull request as draft January 14, 2025 20:07
@tgross35
Copy link
Contributor Author

The test still fails, and I cannot chase down how gimli is getting into the sysroot as non-private. Locally I am testing with submodules updated too.

r? bjorn3

@rust-log-analyzer

This comment has been minimized.

@bors

This comment was marked as outdated.

@bjorn3
Copy link
Member

bjorn3 commented Jan 20, 2025

Maybe you can make the code that checks if a crate is private for diagnostics check if all paths to reach a dependency are private and if so consider the dependency to be private even if the direct dependent crate doesn't mark it as private?

@tgross35
Copy link
Contributor Author

Do you mean to do that as part of the is_private_dep check?

I am apparently missing some path since exposing more traits in builtins seems to leak into diagnostics still #135560. Haven't looked into it yet, but I suppose that might fix it.

@bjorn3
Copy link
Member

bjorn3 commented Jan 23, 2025

Do you mean to do that as part of the is_private_dep check?

Yes

@tgross35 tgross35 force-pushed the stdlib-dependencies-private branch from 560b580 to ee49697 Compare January 28, 2025 21:23
@tgross35
Copy link
Contributor Author

It looks like the reason compiler_builtins is not showing up as private is because it shows up as an extern crate item with a no-location span, which gets picked up at

self.build_reduced_graph_for_item(item);
. I'm still trying to figure out where this would come from.

@tgross35
Copy link
Contributor Author

This looks like a possibility

let item = if name == sym::compiler_builtins {
// compiler_builtins is a private implementation detail. We only
// need to insert it into the crate graph for linking and should not
// expose any of its public API.
//
// FIXME(#113634) We should inject this during post-processing like
// we do for the panic runtime, profiler runtime, etc.
cx.item(
span,
Ident::new(kw::Underscore, ident_span),
thin_vec![],
ast::ItemKind::ExternCrate(Some(name)),
)

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@tgross35 tgross35 force-pushed the stdlib-dependencies-private branch 2 times, most recently from b32d8d1 to 7a6a6cd Compare January 28, 2025 22:45
@rust-log-analyzer

This comment has been minimized.

tgross35 added a commit to tgross35/rust that referenced this pull request Jan 28, 2025
Currently, marking a dependency private does not automatically make all
its child dependencies private. Resolve this by making its children
private by default as well.

[1]: rust-lang#135501 (comment)
tgross35 added a commit to tgross35/rust that referenced this pull request Jan 28, 2025
Currently, marking a dependency private does not automatically make all
its child dependencies private. Resolve this by making its children
private by default as well.

[1]: rust-lang#135501 (comment)
@tgross35 tgross35 force-pushed the stdlib-dependencies-private branch from 5354933 to 9c9ea48 Compare January 28, 2025 23:24
@tgross35
Copy link
Contributor Author

@bors try

@tgross35 tgross35 changed the title [WIP] Mark sysroot dependencies private Resolve compiler_builtins not being treated as private; clean up #135278 Jan 28, 2025
bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 28, 2025
…, r=<try>

Resolve `compiler_builtins` not being treated as private; clean up rust-lang#135278

Follow up of rust-lang#135278

try-job: test-various
@bors

This comment was marked as outdated.

@bors
Copy link
Collaborator

bors commented Feb 20, 2025

⌛ Trying commit 0827f25 with merge 95f832d...

@bors
Copy link
Collaborator

bors commented Feb 20, 2025

☀️ Try build successful - checks-actions
Build commit: 95f832d (95f832deb297cbe86639f86bcc85ba151b687dc5)

@tgross35
Copy link
Contributor Author

@rustbot ready

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Feb 20, 2025
@bjorn3
Copy link
Member

bjorn3 commented Feb 21, 2025

Looks like you still have the DO NOT MERGE commit.

`compiler_builtins` is currently injected as `extern crate
compiler_builtins as _`. This has made gating via diagnostics difficult
because it appears in the crate graph as a non-private dependency, and
there isn't an easy way to differentiate between the injected AST and
user-specified `extern crate compiler_builtins`.

Resolve this by injecting `compiler_builtins` during postprocessing
rather than early in the AST. Most of the time this isn't even needed
because it shows up in `std` or `core`'s crate graph, but injection is
still needed to ensure `#![no_core]` works correctly.

A similar change was attempted at [1] but this encountered errors
building `proc_macro` and `rustc-std-workspace-std`. Similar failures
showed up while working on this patch, which were traced back to
`compiler_builtins` showing up in the graph twice (once via dependency
and once via injection). This is resolved by not injecting if a
`#![compiler_builtins]` crate already exists.

[1]: rust-lang#113634
Remove the portion of ed63539 that automatically sets crates private
based on whether they are dependencies of `std`. Instead, this is
controlled by dependency configuration in `Cargo.toml`.
In [1], most dependencies of `std` and other sysroot crates were marked
private, but this did not happen for `alloc` and `test`. Update these
here, marking public standard library crates as the only non-private
dependencies.

[1]: rust-lang#111076
Currently, marking a dependency private does not automatically make all
its child dependencies private. Resolve this by making its children
private by default as well.

This also resolves some FIXMEs for tests that are intended to fail but
previously passed.

[1]: rust-lang#135501 (comment)
The recent fixes to private dependencies exposed some cases in the UEFI
module where private dependencies are exposed in a public interface.
These do not need to be crate-public, so change them to `pub(crate)`.
@tgross35 tgross35 force-pushed the stdlib-dependencies-private branch from 0827f25 to 9392580 Compare February 21, 2025 17:37
@tgross35
Copy link
Contributor Author

I kept that in case a retest with further changes was needed. Dropped it now and squashed the last fixup.

@bjorn3
Copy link
Member

bjorn3 commented Feb 21, 2025

@bors r+

@bors
Copy link
Collaborator

bors commented Feb 21, 2025

📌 Commit 9392580 has been approved by bjorn3

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 21, 2025
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Feb 22, 2025
…te, r=bjorn3

Inject `compiler_builtins` during postprocessing and ensure it is made private

Follow up of rust-lang#135278

Do the following:

* Inject `compiler_builtins` during postprocessing, rather than injecting `extern crate compiler_builtins as _` into the AST
* Do not make dependencies of `std` private by default (this was added in rust-lang#135278)
* Make sure sysroot crates correctly mark their dependencies private/public
* Ensure that marking a dependency private makes its dependents private by default as well, unless otherwise specified
* Do the `compiler_builtins` update that has been blocked on this

There is more detail in the commit messages. This includes the changes I was working on in rust-lang#136226.

try-job: test-various
try-job: x86_64-msvc-1
try-job: x86_64-msvc-2
try-job: i686-mingw-1
try-job: i686-mingw-2
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Feb 22, 2025
…te, r=bjorn3

Inject `compiler_builtins` during postprocessing and ensure it is made private

Follow up of rust-lang#135278

Do the following:

* Inject `compiler_builtins` during postprocessing, rather than injecting `extern crate compiler_builtins as _` into the AST
* Do not make dependencies of `std` private by default (this was added in rust-lang#135278)
* Make sure sysroot crates correctly mark their dependencies private/public
* Ensure that marking a dependency private makes its dependents private by default as well, unless otherwise specified
* Do the `compiler_builtins` update that has been blocked on this

There is more detail in the commit messages. This includes the changes I was working on in rust-lang#136226.

try-job: test-various
try-job: x86_64-msvc-1
try-job: x86_64-msvc-2
try-job: i686-mingw-1
try-job: i686-mingw-2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-tidy Area: The tidy tool S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants