diff options
author | van Hauser <vh@thc.org> | 2020-08-20 19:00:15 +0200 |
---|---|---|
committer | van Hauser <vh@thc.org> | 2020-08-20 19:00:15 +0200 |
commit | 182b8b3e142814ac865396f8a66453f071d8a2d6 (patch) | |
tree | 3ead8869fefa438aaa84323a4d23fb40a396c754 /docs/env_variables.md | |
parent | 4ce5ed370a1c18c8c7d7f6ad4fa029a34e1326e4 (diff) | |
download | afl++-182b8b3e142814ac865396f8a66453f071d8a2d6.tar.gz |
remove doc reference for SKIPSINGLEBLOCK
Diffstat (limited to 'docs/env_variables.md')
-rw-r--r-- | docs/env_variables.md | 10 |
1 files changed, 3 insertions, 7 deletions
diff --git a/docs/env_variables.md b/docs/env_variables.md index f0ae0b6c..94c34400 100644 --- a/docs/env_variables.md +++ b/docs/env_variables.md @@ -83,17 +83,12 @@ tools make fairly broad use of environmental variables: The native instrumentation helpers (llvm_mode and gcc_plugin) accept a subset of the settings discussed in section #1, with the exception of: - - Setting AFL_LLVM_SKIPSINGLEBLOCK=1 will skip instrumenting - functions with a single basic block. This is useful for most C and - some C++ targets. This works for all instrumentation modes. - - AFL_AS, since this toolchain does not directly invoke GNU as. - TMPDIR and AFL_KEEP_ASSEMBLY, since no temporary assembly files are created. - - AFL_INST_RATIO, as we switched for instrim instrumentation which - is more effective but makes not much sense together with this option. + - AFL_INST_RATIO, as we by default collision free instrumentation is used. Then there are a few specific features that are only available in llvm_mode: @@ -121,7 +116,8 @@ Then there are a few specific features that are only available in llvm_mode: built if LLVM 11 or newer is used. - AFL_LLVM_INSTRUMENT=CFG will use Control Flow Graph instrumentation. - (not recommended!) + (not recommended for afl-clang-fast, default for afl-clang-lto as there + it is a different and better kind of instrumentation.) None of the following options are necessary to be used and are rather for manual use (which only ever the author of this LTO implementation will use). |