summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorpsykose2024-07-10 06:49:02 +0200
committerJulien Voisin2024-07-10 13:20:23 +0000
commit459d202b1bbf7abb817a596ce9374edfb7b4da8f (patch)
treefa32723580731c14f435b4c2dd39e771efe80c62 /README.md
parent936d55d4c263264bc21ccdaeed2537ff0d4320f2 (diff)
prefix special defines with FORTIFY_
just in case, and because 'PEDANTIC_CHECKS' is a really generic name
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 8ea8908..86e73fc 100644
--- a/README.md
+++ b/README.md
@@ -24,10 +24,10 @@ on Clang. It was initially intended to be used on
24- It has a [comprehensive suite of tests](https://github.com/jvoisin/fortify-headers/tree/master/tests), 24- It has a [comprehensive suite of tests](https://github.com/jvoisin/fortify-headers/tree/master/tests),
25 running both on Clang and on GCC for every commit, with 25 running both on Clang and on GCC for every commit, with
26 [significant coverage](https://jvoisin.github.io/fortify-headers/) 26 [significant coverage](https://jvoisin.github.io/fortify-headers/)
27- Defining `USE_NATIVE_CHK` will make use of compiler-provided builtin `_chk` 27- Defining `FORTIFY_USE_NATIVE_CHK` will make use of compiler-provided builtin `_chk`
28 functions, which might be a bit better in term of diagnostics, 28 functions, which might be a bit better in term of diagnostics,
29 but won't necessarily provide the same amount of security checks. 29 but won't necessarily provide the same amount of security checks.
30- Defining `PEDANTIC_CHECKS` will enable pedantic checks, that while technically 30- Defining `FORTIFY_PEDANTIC_CHECKS` will enable pedantic checks, that while technically
31 correct, might break some programs relying on widely accepted 31 correct, might break some programs relying on widely accepted
32 undefined-behaviours. 32 undefined-behaviours.
33 33