-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Tracking Issue for mir-inlining #81567
Copy link
Copy link
Open
Labels
A-mir-optArea: MIR optimizationsArea: MIR optimizationsA-mir-opt-inliningArea: MIR inliningArea: MIR inliningC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC
Metadata
Metadata
Assignees
Labels
A-mir-optArea: MIR optimizationsArea: MIR optimizationsA-mir-opt-inliningArea: MIR inliningArea: MIR inliningC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is a tracking issue for the MIR inliner. You can currently enable it by passing
-Zinline-miror-Zmir-opt-level=3to the compiler (although that also enables a bunch of other opts)About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
#[inline(always)]work even inmir-opt-level=1(mir-opt-level=0 is just a debugging feature, not meant to ever be exposed to users)Implementation history
-Zflags for tuning the MIR inliner heuristiccc @rust-lang/wg-mir-opt