feat(hints): support minimum optimization levels by 0xPoe · Pull Request #17368 · rust-lang/cargo

0xPoe · 2026-08-16T09:10:26Z

What does this PR try to resolve?

This PR would allow Rust library to provide a simple hint about the minimum opt-level to build them with via the hint.min-opt-level setting in the manifest.

How to test and review this PR?

Check the unit tests and review it commit by commit.

r?@ghost

0xPoe

🔢 Self-check (PR reviewed by myself and ready for feedback)

Code compiles successfully
Unit tests added
No AI-generated elegant nonsense in PR.
Comments added where necessary
PR title and description updated
Documentation updated
PR size is reasonable

r?@joshtriplett

View changes since this review

epage · 2026-08-21T20:27:16Z

 via `profile`, which takes precedence, and which can only be specified in the
 top-level crate being built.

+## Package `min-opt-level` hint


Can you have a subsection that is written as-if it was the end-user documentation?

View changes since the review

Could you give an example of the kind of end-user documentation you expect? What should it include? I thought the current document already covered the basic usage and examples.

epage · 2026-08-21T20:27:47Z

+The hint accepts the numeric optimization levels 0, 1, 2, and 3. Other values
+produce a warning and are ignored. If the selected [profile](profiles.md) has a


Why do they produce a warning instead of error?

View changes since the review

If we proceed with errors, does that mean that introducing a new optimization level in the future, which is accepted by the new Cargo, would cause an error with older versions of Cargo? Would this be considered a backward compatibility issue? But I guess introducing a new optimization level might be impossible, especially a numeric optimization level?

epage · 2026-08-21T20:37:59Z

+    let pkg_hint_min_opt_level = match parse_min_opt_level_hint(hints.min_opt_level.as_ref()) {
+        Ok(level) => level,
+        Err(MinOptLevelHintError::OutOfRange(level)) => {
+            unit_capped_warn(&format!(
+                "ignoring unsupported value ({level}) for 'hints.min-opt-level', which only supports integers from 0 to 3"
+            ))?;
+            None
+        }
+        Err(MinOptLevelHintError::WrongType(value_type)) => {
+            unit_capped_warn(&format!(
+                "ignoring unsupported value type ({value_type}) for 'hints.min-opt-level', which expects an integer"
+            ))?;
+            None
+        }
+    };
+    if matches!(pkg_hint_min_opt_level, Some(1..=3)) && !bcx.gctx.cli_unstable().hint_min_opt_level
+    {
+        unit_capped_warn(
+            "ignoring 'hints.min-opt-level', pass `-Zhint-min-opt-level` to enable it",
+        )?;
+    }


Why is this check placed here?

View changes since the review

I simply followed the mostly-unused placement and tried to group them together. However, after reconsidering, this may not make sense because this case differs from it: this hint does not directly change the cmd here. The per-compilation-unit check also does not apply to the min-opt-level hint. I will try to find the right place to perform this check.

epage · 2026-08-21T20:39:59Z

+        let mut profile = maker.get_profile(
+            Some(pkg_id),
+            is_member,
+            unit_for.is_for_host(),
+            min_opt_level,
+        );


Why do we pass it into get_profile, rather than overriding it here?

View changes since the review

Because the hint takes precedence within ProfileMaker::get_profile, applying it afterward would override explicit settings such as:

[profile.dev.package.foo] opt-level = 0

Record the current ignored-hint behavior across the RFC precedence, scope, validation, and boundary cases. Signed-off-by: 0xPoe <poe.liu@pm.me>

RFC 3924 lets a package request a numeric optimization floor without overriding an application's profile choices. Apply the hint after profile and built-in host defaults but before explicit package and build overrides, while leaving the unordered size levels unchanged. Signed-off-by: 0xPoe <poe.liu@pm.me>

Document the unstable gate, accepted range, profile precedence, non-recursive scope, and the narrow cases where packages should request optimization. Include an explicit debugging override so top-level users retain control. Signed-off-by: 0xPoe <poe.liu@pm.me>

rustbot · 2026-08-30T12:29:45Z

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

0xPoe changed the title ~~feat(hints): support minimum optimization levels~~ WIP: feat(hints): support minimum optimization levels Aug 16, 2026

0xPoe changed the title ~~WIP: feat(hints): support minimum optimization levels~~ WIP(Not Ready For Review): feat(hints): support minimum optimization levels Aug 16, 2026

0xPoe force-pushed the hint-min-opt-level branch 7 times, most recently from b532a3f to 2b19c48 Compare August 21, 2026 07:18

0xPoe commented Aug 21, 2026

View reviewed changes

Comment thread crates/cargo-util-schemas/Cargo.toml

Comment thread crates/cargo-util-schemas/manifest.schema.json

Comment thread src/workspace/profiles.rs

rustbot assigned joshtriplett Aug 21, 2026

0xPoe changed the title ~~WIP(Not Ready For Review): feat(hints): support minimum optimization levels~~ feat(hints): support minimum optimization levels Aug 21, 2026

0xPoe marked this pull request as ready for review August 21, 2026 07:20

rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 21, 2026

epage reviewed Aug 21, 2026

View reviewed changes

Comment thread tests/testsuite/hints.rs

epage reviewed Aug 21, 2026

View reviewed changes

Comment thread tests/testsuite/hints.rs

epage reviewed Aug 21, 2026

View reviewed changes

Comment thread tests/testsuite/hints.rs

This comment has been minimized.

Sign in to view

0xPoe force-pushed the hint-min-opt-level branch 2 times, most recently from 14ab0ce to 415812c Compare August 26, 2026 07:53

This comment has been minimized.

Sign in to view

0xPoe force-pushed the hint-min-opt-level branch from 415812c to aaf6533 Compare August 26, 2026 07:56

0xPoe marked this pull request as draft August 26, 2026 07:59

rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 26, 2026

0xPoe added the S-waiting-on-author Status: The marked PR is awaiting some action (such as code changes) from the PR author. label Aug 26, 2026

0xPoe force-pushed the hint-min-opt-level branch 3 times, most recently from 18f313e to ff1b273 Compare August 27, 2026 06:56

0xPoe marked this pull request as ready for review August 27, 2026 07:09

rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 27, 2026

0xPoe requested a review from epage August 27, 2026 07:29

This comment has been minimized.

Sign in to view

0xPoe added 3 commits August 30, 2026 14:22

test(hints): add min-opt-level behavior tests

5fadb35

Record the current ignored-hint behavior across the RFC precedence, scope, validation, and boundary cases. Signed-off-by: 0xPoe <poe.liu@pm.me>

0xPoe force-pushed the hint-min-opt-level branch from ff1b273 to b9ea4de Compare August 30, 2026 12:29

		The hint accepts the numeric optimization levels 0, 1, 2, and 3. Other values
		produce a warning and are ignored. If the selected [profile](profiles.md) has a

Uh oh!

Uh oh!

Conversation

0xPoe commented Aug 16, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR try to resolve?

How to test and review this PR?

Uh oh!

0xPoe left a comment • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

epage Aug 21, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

0xPoe Aug 27, 2026

Choose a reason for hiding this comment

Uh oh!

epage Aug 21, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

0xPoe Aug 24, 2026

Choose a reason for hiding this comment

Uh oh!

epage Aug 21, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

0xPoe Aug 24, 2026

Choose a reason for hiding this comment

Uh oh!

epage Aug 21, 2026 • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

0xPoe Aug 26, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

rustbot commented Aug 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

0xPoe commented Aug 16, 2026 •

edited by rustbot

Loading

0xPoe left a comment •

edited by rustbot

Loading

epage Aug 21, 2026 •

edited by rustbot

Loading

epage Aug 21, 2026 •

edited by rustbot

Loading

epage Aug 21, 2026 •

edited by rustbot

Loading

epage Aug 21, 2026 •

edited by rustbot

Loading