Skip to content

docs: describe -Osize as the default optimization mode in OptimizationTips.rst #65326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 20, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/OptimizationTips.rst
Original file line number Diff line number Diff line change
Expand Up @@ -25,11 +25,11 @@ three different optimization levels:

- ``-Onone``: This is meant for normal development. It performs minimal
optimizations and preserves all debug info.
- ``-O``: This is meant for most production code. The compiler performs
- ``-Osize``: This is meant for most production code. The compiler performs
aggressive optimizations that can drastically change the type and amount of
emitted code. Debug information will be emitted but will be lossy.
- ``-Osize``: This is a special optimization mode where the compiler prioritizes
code size over performance.
- ``-O``: This is a special optimization mode where the compiler prioritizes
performance over code size.

In the Xcode UI, one can modify the current optimization level as follows:

Expand Down