Skip to content

Commit 96290b8

Browse files
committed
Make 'What should you do when compiling compilers?' a top-level section
Signed-off-by: Thomas Nyman <[email protected]>
1 parent 76dcd10 commit 96290b8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/Compiler-Hardening-Guides/Compiler-Options-Hardening-Guide-for-C-and-C++.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1181,7 +1181,7 @@ If the build ID method is used the debug info file’s name is computed from the
11811181

11821182
Note that the build ID does not act as a checksum for the executable or debug info file. For more information on the build ID feature please refer to the GDB[^binutils-objcopy] and GNU linker[^binutils-ld] documentation.
11831183

1184-
### What should you do when compiling compilers?
1184+
## What should you do when compiling compilers?
11851185

11861186
If you are compiling a C/C++ compiler, where practical make the generated compiler's default options the *secure* options. The below table summarizes relevant options that can be specified when building GCC or Clang that affect the defaults of the compiler:
11871187

0 commit comments

Comments
 (0)