-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
38 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
|
||
# Compiler warnings | ||
|
||
* From "[Broken Warnings Theory](https://devblogs.microsoft.com/cppblog/broken-warnings-theory/)": "In our Diagnostics Improvements Survey, 15% of 270 respondents indicated they build their code with /Wall /WX indicating they have a zero tolerance for any warnings." | ||
* From NASA's "[Cyclomatic Complexity and Basis Path Testing Study](https://ntrs.nasa.gov/citations/20205011566)": "Ensure that all code compiles without warnings, with warnings enabled at the highest possible level (e.g., gcc–Wall–pedantic) and map warnings to errors (i.e., compiler warnings stop the build)." and "Requiring that all code be compiled with all available warnings in the compiler enabled at their highest level (e.g., -pedantic), while generating zero warnings." | ||
* "[A Bit on Warnings](https://bignerdranch.com/blog/a-bit-on-warnings/)" by Mark Dalrymple. | ||
* [Best practices regarding warning outputs when compiling in gcc?](https://stackoverflow.com/questions/58903839/best-practices-regarding-warning-outputs-when-compiling-in-gcc) | ||
* [Recommended compiler and linker flags for GCC](https://developers.redhat.com/blog/2018/03/21/compiler-and-linker-flags-gcc) | ||
* [Options That Control Static Analysis](https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Static-Analyzer-Options.html) | ||
* [Guide to predefined macros in C++ compilers (gcc, clang, msvc etc.)](https://blog.kowalczyk.info/article/j/guide-to-predefined-macros-in-c-compilers-gcc-clang-msvc-etc..html) | ||
* [Diagnose useless null statements / empty init-statements](https://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20181203/253703.html) | ||
* [A Few Billion Lines of Code Later: Using Static Analysis to Find Bugs in the Real World](https://cacm.acm.org/magazines/2010/2/69354-a-few-billion-lines-of-code-later/fulltext) | ||
* [Clang command line argument reference](https://clang.llvm.org/docs/ClangCommandLineReference.html) | ||
* [GCC Command Options](https://gcc.gnu.org/onlinedocs/gcc/Invoking-GCC.html) | ||
|
||
# Build madness | ||
|
||
* [An introduction to deterministic builds with C/C++](https://blog.conan.io/2019/09/02/Deterministic-builds-with-C-C++.html) | ||
* [Build faster with Buck2: Our open source build system](https://engineering.fb.com/2023/04/06/open-source/buck2-open-source-large-scale-build-system/) |