-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
rustc_force_inline used in core fails when called from alloc #148915
Copy link
Copy link
Open
Labels
A-mir-opt-inliningArea: MIR inliningArea: MIR inliningT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.requires-internal-featuresThis issue requires the use of internal features.This issue requires the use of internal features.requires-nightlyThis issue requires a nightly compiler in some way. When possible, use a F-* label instead.This issue requires a nightly compiler in some way. When possible, use a F-* label instead.
Metadata
Metadata
Assignees
Labels
A-mir-opt-inliningArea: MIR inliningArea: MIR inliningT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.requires-internal-featuresThis issue requires the use of internal features.This issue requires the use of internal features.requires-nightlyThis issue requires a nightly compiler in some way. When possible, use a F-* label instead.This issue requires a nightly compiler in some way. When possible, use a F-* label instead.
Type
Fields
Give feedbackNo fields configured for issues without a type.
In #148725 I tried to use
rustc_force_inline(cc #134082) on the followingsince it's only called directly to constrain type inference, and is never allowed to be called by users.
However, it failed in CI because https://triage.rust-lang.org/gha-logs/rust-lang/rust/55265405601
I would have expected this to work -- why wouldn't we have MIR for
corewhen compilingalloc? -- so figured I'd file the bug even though it's an internal feature. This is the kind of place where I'd really like to use the feature incore, after all.Makes me wonder if there's something odd about cycle checking going on, or similar?