Skip to content

Changing -O to opt-level=3 #828

Closed
Closed

Description

@clubby789

Proposal

The -O flag has existed for over 14 years, predating opt-levels entirely. It is somewhat surprising that it means opt-level=2, especially as Cargo's release profile uses level 3.

In C compilers, -O usually means a non-maximum opt level as some optimizations can cause unsoundness; Rust doesn't have this limitation. (Not sure this part is true)

I'd like to propose changing this shorthand flag to a more useful default.

Process

The main points of the Major Change Process are as follows:

  • File an issue describing the proposal.
  • A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
    • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
    • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
  • Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

Activity

  1. added
    major-changeA proposal to make a major change to rustc
    T-compilerAdd this label so rfcbot knows to poll the compiler team
    on Jan 14, 2025
  2. rustbot commented on Jan 14, 2025

    @rustbot
    Collaborator

    This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

    Concerns or objections to the proposal should be discussed on Zulip and formally registered here by adding a comment with the following syntax:

    @rfcbot concern reason-for-concern 
    <description of the concern> 
    

    Concerns can be lifted with:

    @rfcbot resolve reason-for-concern 
    

    See documentation at https://forge.rust-lang.org

    cc @rust-lang/compiler

  3. Noratrieb commented on Jan 14, 2025

    @Noratrieb
    Member

    @rustbot second

  4. added
    final-comment-periodThe FCP has started, most (if not all) team members are in agreement
    on Jan 14, 2025
  5. apiraino commented on Jan 27, 2025

    @apiraino
    Contributor

    @rustbot label -final-comment-period +major-change-accepted

  6. added
    to-announceAnnounce this issue on triage meeting
    and removed
    final-comment-periodThe FCP has started, most (if not all) team members are in agreement
    on Jan 27, 2025
  7. added 4 commits that reference this issue on Feb 6, 2025
  8. added a commit that references this issue on Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-compilerAdd this label so rfcbot knows to poll the compiler teammajor-changeA proposal to make a major change to rustcmajor-change-acceptedA major change proposal that was accepted

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions