Use -O2 compilation for Autocorrect only

[Camyll]

Summary:
Apply -02 compiler flag to make FLLM autocorrect faster

Sheet measuring different scopes of applying -02 and the resulting latency
https://docs.google.com/spreadsheets/d/1ZnxoRwCIiMz3hXyhgb6sm_2UThBUyq-mpp8RzksfJMQ/edit?usp=sharing

Differential Revision: D85152814

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15425

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ROCm failures during provisioning step due to network issues

❌ 10 New Failures

As of commit 8f66a03 with merge base 7741e70 ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  RuntimeError: Command docker exec -t 4233928e84baef49ca20f4dab23106f723d99386af0d66f478e8e9ab1531907e /exec failed with exit code 3
• periodic / test-models-linux (buck2, mv3, portable, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command docker exec -t 7c20a8f0d366f60b5e3012de96dceccd7045d224da75e3eabaa7d4c6a3693ae9 /exec failed with exit code 3
• periodic / test-models-linux (buck2, mv3, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh)
  RuntimeError: Command docker exec -t c9e093e3f983832005dd00265feedda685d0069bd57157d8c437c3f7f7b55a85 /exec failed with exit code 3
• pull / android / build-llm-demo / linux-job (gh)
  RuntimeError: Command docker exec -t 2045f970ff17aa1d07c1068fccf2be2b2ae0b86200e559cbd35071cc87f3c5a9 /exec failed with exit code 3
• pull / test-models-linux-basic (mv3, portable, buck2, linux.2xlarge, executorch-ubuntu-22.04-clang12) / linux-job (gh)
  RuntimeError: Command docker exec -t 35f7ac85746ad049823fb9a86c3cbbfad613063621de8115bc5e3c68937d3c03 /exec failed with exit code 3
• pull / test-models-linux-basic (mv3, xnnpack-quantization-delegation, buck2, linux.2xlarge, executorch-u... / linux-job (gh)
  RuntimeError: Command docker exec -t ab8613b0487bc2dc24245fb9a7ca5fe5566101ba24371a50a47bd62e5d590c9c /exec failed with exit code 3
• pull / test-models-linux-basic (vit, portable, buck2, linux.2xlarge, executorch-ubuntu-22.04-clang12) / linux-job (gh)
  RuntimeError: Command docker exec -t ab733e650840a0b64f84ac22b53efcf1c1472294daceb0eaefb023f08ce9fd57 /exec failed with exit code 3
• pull / test-models-linux-basic (vit, xnnpack-quantization-delegation, buck2, linux.2xlarge, executorch-u... / linux-job (gh)
  RuntimeError: Command docker exec -t ea3c60711e3f8b5958570c3634b34cbe1a3cf6a382cf30d00e3dbb3c6c2dfe4d /exec failed with exit code 3
• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t b17db3ebcb7f712a23871838670426511613b181112ce7bbca8484d19c45f863 /exec failed with exit code 3
• pull / unittest-buck / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@Camyll has exported this pull request. If you are a Meta employee, you can view the originating Diff in D85152814.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[meta-cla]

Hi @Camyll!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[lucylq]

hmn, not seeing this be commented out. It should look like the examples on line 102-112, or this: #15582

[lucylq]

Closing as duplicate of #15583