similar to: [LLVMdev] llvm library linking issues

The output of `llvm-config --cppflags --ldflags --libs core support` and `llvm-config --cppflags --ldflags --libs core` is the same. I've also tried specifying -lLLVMSupport manually. Same result.  --Eugene ----- Original Message -----  Hi Eugene, >I do this, and I've tried a few variations of on it: >clang++ `llvm-config --cppflags --ldflags --libs core` -o clangtest

Eugene, how about below? $ clang clangtest.cpp `llvm-config --ldflags --libs core` (I guess linking order would be) 2012/7/18 Eugene <code_ep at yahoo.com>: > The output of `llvm-config --cppflags --ldflags --libs core support` and > `llvm-config --cppflags --ldflags --libs core` is the same. I've also tried specifying -lLLVMSupport manually. Same result. > > --Eugene >

I do this, and I've tried a few variations of on it: clang++ `llvm-config --cppflags --ldflags --libs core`  -o clangtest clangtest.cpp I've also tried removing the library and the include file in turn, which in both cases succefully made the compiler not find the files needed. ----- Original Message ----- Hi Eugene, On 17/07/12 03:46, Eugene wrote: > I'm trying to make use of

Hi Eugene, > I do this, and I've tried a few variations of on it: > clang++ `llvm-config --cppflags --ldflags --libs core` -o clangtest clangtest.cpp the missing routine is defined in the support library, not the core library, try --libs core support Ciao, Duncan. > > I've also tried removing the library and the include file in turn, which in both cases succefully made the

Hi Eugene, On 17/07/12 03:46, Eugene wrote: > I'm trying to make use of the llvm compiler libraries, but I can't get them to link to my program correctly. > > #include <llvm/Constants.h> > #include <llvm/DerivedTypes.h> > > > int main(){ > > llvm::APInt(1,0); > > return 0; > } > > I get an error like: > undefined reference to

Le Thu, May 03, 2007 at 09:36:22AM -0700, Chris Lattner écrivait/wrote: > On Thu, 3 May 2007, Basile STARYNKEVITCH wrote: > > > > > FWIW, the latest gcc snapshot from yesterday gcc version 4.3.0 20070501 > > (experimental) fail to compile latest LLVM (with compile errors!). > > Please file an llvm bug report with these errors. It may be that we are > doing

On Thu, 3 May 2007, Basile STARYNKEVITCH wrote: > > What version of g++ is usable to compile the latest LLVM CVS snapshot on a > Linux/x86-64 (AMD64) Debian/ Sid or Etch plateform? Please look here: http://llvm.org/docs/GettingStarted.html#brokengcc I'd suggest late versions of GCC 4.0.x. The 4.1 series has had numerous problems compiling LLVM on x86-64, though some people have

Hello All, What version of g++ is usable to compile the latest LLVM CVS snapshot on a Linux/x86-64 (AMD64) Debian/ Sid or Etch plateform? What compiler do LLVM dzevelopers use to compile LLVM on Linux/X86-64 systems? IKt seems that most versions of g++ fail to compile LLVM and that some others compile it wrongly (producing buggy code)? Why can't g++-4.1 be used? FWIW, the latest gcc

On Jan 20, 2009, at 1:22 AM, Jay Foad wrote: >>> I realise that the DataTypes.h.in part might be controversial. Also, >>> there's probably a better place to put it, but I'm not sure where. >> >> I didn't apply this part. What problems does it cause to not have >> this? Can we fix uses of max and min? > > I could try to fix this by changing

Hi, I'm cross compiling (BUILD=darwin, HOST=i386-mingw32) LLVM with llvm-gcc (both from current mainline). Everything works fine, except that I get a lot of warnings of the following type: [..]/lib/gcc/i386-mingw32/4.2.1/../../../../i386-mingw32/bin/ld: /[..]/build-llvm/Release/lib/libLLVMSupport.a(APInt.o): warning: duplicate section `.text$linkonce__ZN4llvm5APInt17getSignedMinValueEj'

>> I realise that the DataTypes.h.in part might be controversial. Also, >> there's probably a better place to put it, but I'm not sure where. > > I didn't apply this part. What problems does it cause to not have > this? Can we fix uses of max and min? I get these errors in lib: .../lib/Analysis/ValueTracking.cpp:162: error: no matching function for call to

Hi Dan, Thank you for your advice on the build/install. On Jun 11, 2014, at 7:06 PM, Dan Liew <dan at su-root.co.uk> wrote: > Well on many Linux distributions LLVM and Clang are installable as > packages (along with the header files) so for something like the > Kaleidoscope tutorial it isn't necessary to build LLVM and Clang from > source. However you are running OSX

On Jun 12, 2014, at 4:37 PM, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > > > On 6/12/14, 3:07 PM, Joseph wrote: >> Hi Dan, >> >> >> So now that the includes are being found building the tutorial results in 74 warnings and 20 errors. Heres a couple examples: >> >> In file included from

> /[..]/lib/gcc/i386-mingw32/4.2.1/../../../../i386-mingw32/bin/ld: > /[..]/build-llvm/Release/lib/libLLVMSupport.a(APInt.o): warning: > duplicate section `.text$linkonce__ZNK4llvm5APIntngEv' has > different size > > Is this normal/known? Yes, this is known problem. In fact it was here for ages, but previously we just grabbed one "instance" of linkonce function

OK, the code for sdivrem in APInt.h is wrong. Here's what's written: static void sdivrem(const APInt &LHS, const APInt &RHS, APInt &Quotient, APInt &Remainder) { if (LHS.isNegative()) { if (RHS.isNegative()) APInt::udivrem(-LHS, -RHS, Quotient, Remainder); else APInt::udivrem(-LHS, RHS, Quotient, Remainder); Quotient =

Hola LLVMers, I'm debugging through some strangeness that I'm seeing on X64 on windows with LLVM2.2. I had to change the code so that it would engage the x64 target machine on windows builds, but I've otherwise left LLVM 2.2 alone. The basic idea is that I've got a function bar which is compiled by VStudio and I'm creating another function foo via LLVM JIT which is going

I wrote the following bit of code static APInt FloorOfQuotient(APInt a, APInt b) { unsigned bits = a.getBitWidth(); APInt q(bits, 1), r(bits, 1); APInt::sdivrem(a, b, q, r); * errs() << "sdivrem(" << a << ", " << b << ") = (" << q << ", " << r << ")\n"; * if (r == 0) return q; else {

Hi, I want to compute the bitwise 'and' between two values of type int1:  %x = and %a, %b  . Which is the LLVM instruction that creates this? I only found the APInt class, whose constructor is:  APInt(unsigned numBits, uint64_t val, bool isSigned = false) and which provides the bitwise AND operation: APInt  llvm::APIntOps::And (const APInt &LHS, const APInt &RHS)   Bitwise

This adds a bunch of static functions that implement unsigned two's complement bignum arithmetic. They could be used to implement much of APInt, but the idea is they are enough to implement APFloat as well, which the current APInt interface is not suited for. Neil. -------------- next part -------------- Index: include/llvm/ADT/APInt.h

On Wed, Nov 30, 2011 at 10:42 PM, Chris Lattner <clattner at apple.com> wrote: > On Nov 29, 2011, at 12:26 AM, David Blaikie wrote: >> For a bit of an experiment I've been trying to compile LLVM & Clang >> with -Weverything (disabling any errors that seem like more noise/less >> interesting). One warning I've recently hit a few instances of is >>