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

Add GLIBCXX_ASSERTIONS to recommended compiler flags #158

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Add GLIBCXX_ASSERTIONS to recommended compiler flags #158

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions 02-Use_the_Tools_Available.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,7 @@ You should use as many compilers as you can for your platform(s). Each compiler
* `-Wformat=2` warn on security issues around functions that format output (i.e., `printf`)
* `-Wlifetime` (only special branch of Clang currently) shows object lifetime issues
* `-Wimplicit-fallthrough` Warns when case statements fall-through. (Included with `-Wextra` in GCC, not in clang)
* `-D_GLIBCXX_ASSERTIONS` (only in GCC >= TBD) Adds extra assertions, null pointer checks. Do not enable this on release builds because it is slow.

Consider using `-Weverything` and disabling the few warnings you need to on Clang

Expand Down