search for: llvm_no_dead_strip

Displaying 11 results from an estimated 11 matches for "llvm_no_dead_strip".

2017 Aug 24
3
Building LLVM's fuzzers
...c-tables, will do soon) > Do you know what's the analog of Wl,-dead_strip on Linux? Apparently -Wl,—gc-sections. For some reason LLVM does not do it for gold, even though it seems to support this flag as well. (that could be another reason why you don’t see the failure on Linux) 1 if(NOT LLVM_NO_DEAD_STRIP) 2 if(${CMAKE_SYSTEM_NAME} MATCHES "Darwin") 3 # ld64's implementation of -dead_strip breaks tools that use plugins. 4 set_property(TARGET ${target_name} APPEND_STRING PROPERTY 5 LINK_FLAGS " -Wl,-dead_strip") 6 elseif(${CMAKE_SYSTEM_NAME} M...
2017 Aug 24
2
Building LLVM's fuzzers
...ead_strip on Linux? >> >> >> Apparently -Wl,—gc-sections. >> For some reason LLVM does not do it for gold, even though it seems to >> support this flag as well. >> (that could be another reason why you don’t see the failure on Linux) >> >> 1 *if*(NOT LLVM_NO_DEAD_STRIP) >> 2 *if*(${CMAKE_SYSTEM_NAME} MATCHES "Darwin") >> 3 # ld64's implementation of -dead_strip breaks tools that use >> plugins. >> 4 set_property(TARGET ${target_name} APPEND_STRING PROPERTY >> 5 LINK_FLAGS " -Wl,-dead_...
2017 Aug 24
3
Building LLVM's fuzzers
...s/HandleLLVMOptions.cmake > @@ -665,6 +665,9 @@ if(LLVM_USE_SANITIZER) > endif() > if (LLVM_USE_SANITIZE_COVERAGE) > append("-fsanitize=fuzzer-no-link" CMAKE_C_FLAGS CMAKE_CXX_FLAGS) > + > + # Dead stripping messes up coverage instrumentation. > + set(LLVM_NO_DEAD_STRIP ON) > endif() > endif() > > Any arguments against that? We shouldn't do this. We really only want to prevent dead stripping of the counters themselves - disabling it completely isn't very nice. > Apparently, a better way is to follow ASAN instrumentation pass, > whic...
2017 Aug 24
4
Building LLVM's fuzzers
...; Apparently -Wl,—gc-sections. >> >> For some reason LLVM does not do it for gold, even though it seems to >> >> support this flag as well. >> >> (that could be another reason why you don’t see the failure on Linux) >> >> >> >> 1 *if*(NOT LLVM_NO_DEAD_STRIP) >> >> 2 *if*(${CMAKE_SYSTEM_NAME} MATCHES "Darwin") >> >> 3 # ld64's implementation of -dead_strip breaks tools that use >> >> plugins. >> >> 4 set_property(TARGET ${target_name} APPEND_STRING PROPERTY >> >> 5...
2017 Aug 24
3
Building LLVM's fuzzers
...gt;> >> For some reason LLVM does not do it for gold, even though it seems to >>>> >> support this flag as well. >>>> >> (that could be another reason why you don’t see the failure on Linux) >>>> >> >>>> >> 1 *if*(NOT LLVM_NO_DEAD_STRIP) >>>> >> 2 *if*(${CMAKE_SYSTEM_NAME} MATCHES "Darwin") >>>> >> 3 # ld64's implementation of -dead_strip breaks tools that use >>>> >> plugins. >>>> >> 4 set_property(TARGET ${target_name} APPEND_STRIN...
2017 Aug 25
2
Building LLVM's fuzzers
...do it for gold, even though it > seems to > >>>>> >> support this flag as well. > >>>>> >> (that could be another reason why you don’t see the failure on > Linux) > >>>>> >> > >>>>> >> 1 *if*(NOT LLVM_NO_DEAD_STRIP) > >>>>> >> 2 *if*(${CMAKE_SYSTEM_NAME} MATCHES "Darwin") > >>>>> >> 3 # ld64's implementation of -dead_strip breaks tools that > use > >>>>> >> plugins. > >>>>> >> 4 set_pr...
2017 Aug 24
5
Building LLVM's fuzzers
(kcc, george: sorry for the re-send, the first was from a non-list email address) My configuration for building the fuzzers in the LLVM tree doesn't seem to work any more (possibly as of moving libFuzzer to compiler-rt, but there have been a few other changes in the last week or so that may be related). I'm building with a fresh top-of-tree clang and setting -DLLVM_USE_SANITIZER=Address
2017 Sep 11
2
Building LLVM's fuzzers
...ms to >>> >>>>> >> support this flag as well. >>> >>>>> >> (that could be another reason why you don’t see the failure on >>> Linux) >>> >>>>> >> >>> >>>>> >> 1 *if*(NOT LLVM_NO_DEAD_STRIP) >>> >>>>> >> 2 *if*(${CMAKE_SYSTEM_NAME} MATCHES "Darwin") >>> >>>>> >> 3 # ld64's implementation of -dead_strip breaks tools that >>> use >>> >>>>> >> plugins. >>> &gt...
2019 Apr 18
3
Opt plugin linkage
...ine Analysis BitWriter CodeGen Core MC MCJIT Object OrcJIT Interpreter RuntimeDyld Coroutines IPO IRReader InstCombine Instrumentation MC ObjCARCOpts ScalarOpts Support Target TransformUtils Vectorize Passes ExecutionEngine ) # Support plugins. set(LLVM_NO_DEAD_STRIP 1) add_llvm_tool(opt AnalysisWrappers.cpp BreakpointPrinter.cpp Debugify.cpp GraphPrinters.cpp NewPMDriver.cpp PassPrinters.cpp PrintSCC.cpp opt.cpp DEPENDS intrinsics_gen ) export_executable_symbols(opt) if(WITH_POLLY AND LINK_POLLY_INTO_TOOLS) target_link_libraries(opt...
2019 Apr 16
2
Opt plugin linkage
Hey: I spent sometime debugging this, it seems like editing ``llvm/tools/opt.cpp`` and move ``cl::ParseCommandLineOptions(argc, argv, "llvm .bc -> .bc modular optimizer and analysis printer\n");`` to the beginning of main() solved it for me. I'm not sure if this is a bug on LLVM side Zhang ------------------ Original ------------------ From: "Viktor Was BSc via
2017 Aug 22
5
[RFC] mir-canon: A new tool for canonicalizing MIR for cleaner diffing.
Patch for review. On Mon, Aug 21, 2017 at 11:45 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> wrote: > Ping. > > Still working on preparing code for review. Will have a patch for review > ready in the coming days. > > PL > > On Tue, Aug 15, 2017 at 12:06 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> > wrote: > >> Hi, >> >> >>