From 0281872ddf5f7b5058770eee610ea5250b82cc01 Mon Sep 17 00:00:00 2001 From: Andrea Fioraldi Date: Wed, 5 Aug 2020 13:05:30 +0200 Subject: remove shared_linking check --- llvm_mode/afl-clang-fast.c | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) (limited to 'llvm_mode/afl-clang-fast.c') diff --git a/llvm_mode/afl-clang-fast.c b/llvm_mode/afl-clang-fast.c index 1aa42150..e0b33475 100644 --- a/llvm_mode/afl-clang-fast.c +++ b/llvm_mode/afl-clang-fast.c @@ -568,18 +568,12 @@ static void edit_params(u32 argc, char **argv, char **envp) { } - if (preprocessor_only || shared_linking) { + if (preprocessor_only) { /* In the preprocessor_only case (-E), we are not actually compiling at all but requesting the compiler to output preprocessed sources only. We must not add the runtime in this case because the compiler will simply output its binary content back on stdout, breaking any build - systems that rely on a separate source preprocessing step. - The shared_linking case (-shared) is more complex. This flag should - only be passed when linking a shared object. When loading such a shared - object into a binary that has also been built with AFL, two AFL runtimes - will exist side-by-side. This is only a problem in the dynamic loading - case because for static linking, the compiler can de-duplicate the - runtime. We must hence avoid attaching the runtime to shared objects. */ + systems that rely on a separate source preprocessing step. */ cc_params[cc_par_cnt] = NULL; return; -- cgit 1.4.1