more detail to the fact that LTO mode can fail easily

2 files changed, 8 insertions, 4 deletions

diff --git a/llvm_mode/README.lto.md b/llvm_mode/README.lto.md
index 052a8ad2..66d0de79 100644
--- a/llvm_mode/README.lto.md
+++ b/llvm_mode/README.lto.md
@@ -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
 
diff --git a/llvm_mode/afl-clang-fast.c b/llvm_mode/afl-clang-fast.c
index 849a4417..14ce00f8 100644
--- a/llvm_mode/afl-clang-fast.c
+++ b/llvm_mode/afl-clang-fast.c
@@ -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");