more detail to the fact that LTO mode can fail easily

This commit is contained in:
van Hauser
2020-03-09 08:33:08 +01:00
parent 36ce9c1fb9
commit 6a6dd84b39
2 changed files with 8 additions and 4 deletions

View File

@ -2,13 +2,16 @@
## TLDR;
1. Use afl-clang-lto/afl-clang-lto++ because it is faster and gives better
1. This compile mode is very frickle if it works it is amazing, if it fails
- well use afl-clang-fast
2. Use afl-clang-lto/afl-clang-lto++ because it is faster and gives better
coverage than anything else that is out there in the AFL world
2. You can use it together with llvm_mode: laf-intel and whitelisting
3. You can use it together with llvm_mode: laf-intel and whitelisting
features and can be combined with cmplog/Redqueen
3. It only works with llvm 9 (and likely 10+ but is not tested there yet)
4. It only works with llvm 9 (and likely 10+ but is not tested there yet)
## Introduction and problem description

View File

@ -610,7 +610,8 @@ int main(int argc, char** argv, char** envp) {
callname, BIN_PATH, BIN_PATH, LLVM_VERSION, LLVM_BINDIR);
if (strcmp(callname, "afl-clang-lto") == 0)
SAYF("Compiled with linker target \"%s\" and LTO flags \"%s\"\n",
SAYF("Compiled with linker target \"%s\" and LTO flags \"%s\"\n\n"
"If anything fails - be sure to read README.lto.md!\n\n",
AFL_REAL_LD, AFL_CLANG_FLTO);
SAYF("\n");