Trevor Gross 1412cfc987 Inject compiler_builtins during postprocessing rather than via AST ... `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]: https://github.com/rust-lang/rust/pull/113634		2025-02-21 17:37:03 +00:00
..
src	Inject compiler_builtins during postprocessing rather than via AST	2025-02-21 17:37:03 +00:00
Cargo.toml	rename rustc_attr to rustc_attr_parsing and create rustc_attr_data_structures	2024-12-16 19:08:19 +01:00
messages.ftl	Inject compiler_builtins during postprocessing rather than via AST	2025-02-21 17:37:03 +00:00