Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify why -O2 #331

Open
david-a-wheeler opened this issue Dec 1, 2023 · 1 comment
Open

Clarify why -O2 #331

david-a-wheeler opened this issue Dec 1, 2023 · 1 comment
Labels
ok to close? Product: Compiler Hardening Guide

Comments

@david-a-wheeler
Copy link
Contributor

There's no separate entry for -O2 in the hardening guide. We should add one. In particular, it doesn't have to be -O2, -O3 is also fine. The reason for at least level 2 is that some of the other hardening mechanisms require it. We document that in their own points, but I think there also needs to be a short discussion about -O all by itself.
@SecurityCRob
Copy link
Contributor

Has this been addressed by the C/C++ Compiler Hardening options guide? @gkunz @thomasnyman @david-a-wheeler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ok to close? Product: Compiler Hardening Guide
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thomasnyman @david-a-wheeler @SecurityCRob