search for: llvm_library_visibility

...e following error, when linking lli, llc, opt, or libLTO.so: `LLVMX86CompilationCallback2' referenced in section `.text' of /tmp/cclv7BYB.ltrans0.ltrans.o: defined in discarded section `.text' of X86JITInfo.o (symbol from plugin) collect2: error: ld returned 1 exit status Removing the LLVM_LIBRARY_VISIBILITY attribute for LLVMX86CompilationCallback2 make the link pass for lli, llc, and opt, but not for libLTO.so. Any ideas why this happens? /Patrik Hägglund

...+339,8 @@ extern "C" { /// must locate the start of the stub or call site and pass it into the JIT /// compiler function. extern "C" { +LLVM_ATTRIBUTE_USED // Fix gcc -flto builds. gcc's LTO (as of 4.8.1) don't sees + // references from inline asm. LLVM_LIBRARY_VISIBILITY void LLVMX86CompilationCallback2(intptr_t *StackPtr, intptr_t RetAddr) { intptr_t *RetAddrLoc = &StackPtr[1]; (However, I still can't link unittest programs, because of the use of anchor methods in CommandLine. I will take a look...

Hi all, I'm currently trying to use clang to build a largish project on Windows using MinGW. I'm currently performing all of the compilation using g++, and then linking with clang++ with lld (due to separate issues I'm having with compiling with clang with MinGW). Compiling with g++ and then linking with clang+lld seems to work fine for small programs. I'm invoking clang++

Hi, I am trying to add a small new backend for LLVM. For assembly printing, I have derived a class from AsmTarget, struct LLVM_LIBRARY_VISIBILITY Asd_ARMAsmPrinter : public AsmPrinter After creating all the bits and pieces, I was trying to use this to print the assembly for a sample program. Though I was getting weird errors. I tried looking for the problem and found that the my target AsmPrinter is not being registered properly. This concl...

...> $ git diff > diff --git a/clang/lib/Driver/ToolChains/MinGW.h > b/clang/lib/Driver/ToolChains/MinGW.h > index 08298e910eb..41c466337b7 100644 > --- a/clang/lib/Driver/ToolChains/MinGW.h > +++ b/clang/lib/Driver/ToolChains/MinGW.h > @@ -34,7 +34,7 @@ public: > >  class LLVM_LIBRARY_VISIBILITY Linker : public Tool { >  public: > -  Linker(const ToolChain &TC) : Tool("MinGW::Linker", "linker", TC) {} > +  Linker(const ToolChain &TC) : Tool("MinGW::Linker", "linker", TC, > RF_Full) {} > >    bool hasIntegratedCPP() const ov...

Hi, We are now about halfway between the 3.4 and 3.5 releases, and I would like to start preparing for a 3.4.1 release. Here is my proposed release schedule: Mar 26 - April 9: Identify and backport additional bug fixes to the 3.4 branch. April 9 - April 18: Testing Phase April 18: 3.4.1 Release How you can help: - If you have any bug fixes you think should be included to 3.4.1, send me an

Hi Sanjay, Thanks, I saw this flag and it's definitely should be considered, but it appeared to me to be static characteristic of target platform. I'm not sure how appropriate it would be to change its value from a front-end. It says "Has", while optional flag would rather say "Uses" meaning that implementation cares about floating point exceptions. Regards, Sergey

...F->hasFnAttribute(Attribute::SanitizeAddress); } diff --git a/lib/Transforms/InstCombine/InstCombine.h b/lib/Transforms/InstCombine/InstCombine.h index 6c0d4e7..d18309d 100644 --- a/lib/Transforms/InstCombine/InstCombine.h +++ b/lib/Transforms/InstCombine/InstCombine.h @@ -102,6 +102,7 @@ class LLVM_LIBRARY_VISIBILITY InstCombiner bool MadeIRChange; LibCallSimplifier *Simplifier; bool MinimizeSize; + bool HonorFPExceptions; public: /// Worklist - All of the instructions that need to be simplified. @@ -115,6 +116,7 @@ public: static char ID; // Pass identification, replacement for typeid Ins...