-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Support miriflags in [target] configuration #17079
Copy link
Copy link
Open
Labels
C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-triageStatus: This issue is waiting on initial triage.Status: This issue is waiting on initial triage.
Metadata
Metadata
Assignees
Labels
C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-triageStatus: This issue is waiting on initial triage.Status: This issue is waiting on initial triage.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
I've been trying to use
-Znext-solver=globallyrecently and due to how invasive it is, I ended up specifying it in the configuration file for bothrustflagsandrustdocflags. Unfortunately,miriflags(to mirrorMIRIFLAGSenvironment variable) isn't supported at the moment.Proposed Solution
Support
miriflagsunder[target]configuration in the config file alongside existingrustflagsandrustdocflags, such that it is possible to do this:Notes
I have no idea why
-Znext-solver=globallyisn't inherited fromrustflagsfor both, but that is a separate issue (for example, #17045).