8000 Consider exposing `target_feature` option in cargo CLI · Issue #14524 · rust-lang/cargo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
10000
Consider exposing target_feature option in cargo CLI #14524
Open
@Kixunil

Description

@Kixunil

Problem

When testing with miri one often has to enable target features (all SIMD features) to be sure to test SIMD instructions which tend to contain unsafe code. This requires target_feature to be set in both RUSTFLAGS and RUSTDOCFLAGS. Not only is this annoying but also a footgun. From my understanding miri just passes the arguments along so it's a cargo issue.

Proposed Solution

Consider adding an argument that can set the target features as needed. Even better, also have an argument that enables all SIMD features.

Alternatively it could be decided that this is too niche and should be handled by miri and that may be the only tool that currently needs it, in which case I'll be happy to open an issue there.

Notes

I've opened this as requested in #12739 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-needs-designStatus: Needs someone to work further on the design for the feature or fix. NOT YET accepted.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0