similar to: [LLVMdev] Build Error from Intrinsics.td

On 9/11/12 4:53 PM, Ryan Taylor wrote: > Tried a fresh checkout with the same issue. I'm assuming this issue > must be on my end. Dumb question: do you have a restrictive ulimit setting that might cause the tblgen program to run out of memory? I tend to doubt that this is the case, but it'd be good to double check. -- John T. > > ---------- Forwarded message ----------

ulimit -s = 8192 set "ulimit -c unlimited" On Tue, Sep 11, 2012 at 3:03 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > John, > > Thanks for responding. No, I don't see a limit from ulimit. It's > definitely with the tblgen though, I have the same errors trying to compile > clang. > > > On Tue, Sep 11, 2012 at 2:57 PM, John Criswell

Tried a fresh checkout with the same issue. I'm assuming this issue must be on my end. ---------- Forwarded message ---------- From: Ryan Taylor <ryta1203 at gmail.com> Date: Tue, Sep 11, 2012 at 1:28 PM Subject: Build Error from Intrinsics.td To: llvmdev at cs.uiuc.edu gmake[1]: Entering directory `/home/ryan/llvm/llvm_core/trunk/lib/VMCore' llvm[1]: Building Intrinsics.gen.tmp

Usually it is the ones that end in ".inc". From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Ryan Taylor Sent: Tuesday, September 11, 2012 3:12 PM To: John Criswell Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Fwd: Build Error from Intrinsics.td What files are created by the TableGen so that I can clean them out and start fresh? On Tue, Sep

John, Thanks for responding. No, I don't see a limit from ulimit. It's definitely with the tblgen though, I have the same errors trying to compile clang. On Tue, Sep 11, 2012 at 2:57 PM, John Criswell <criswell at illinois.edu>wrote: > On 9/11/12 4:53 PM, Ryan Taylor wrote: > > Tried a fresh checkout with the same issue. I'm assuming this issue must > be on my

Here's another question. It's failing on a clean checkout, so what does llvm use from a previous install that I would need to clean when installing a new clean checkout? On Tue, Sep 11, 2012 at 3:27 PM, Villmow, Micah <Micah.Villmow at amd.com>wrote: > Usually it is the ones that end in ".inc".**** > > ** ** > > *From:* llvmdev-bounces at cs.uiuc.edu

What files are created by the TableGen so that I can clean them out and start fresh? On Tue, Sep 11, 2012 at 3:11 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > ulimit -s = 8192 > set "ulimit -c unlimited" > > > > On Tue, Sep 11, 2012 at 3:03 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > >> John, >> >> Thanks for responding. No,

Sorry, here's something a little more descript: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 20 file size (blocks, -f) unlimited pending signals (-i) 16382 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024

I am getting a build error after doing a "make update" and then running "make clean all": gmake[4]: *** No rule to make target `/home/ryan/llvm/llvm_core/trunk/Release+Asserts/lib/ocaml/llvm.cmi', needed by `/home/ryan/llvm/llvm_core/trunk/bindings/ocaml/transforms/ipo/Release+Asserts/llvm_ipo.cmi'. Stop. gmake[4]: Leaving directory

Hi Ryan, Sometimes the configure machinery can get confused. I haven't seen this particular error, so I don't know for sure if that's happening here, though. Try running "./config.status" from the build directory. Perhaps unrelated, but it looks like you're building inside the source tree. I'd recommend not doing that, as it's not too uncommon for that to run

llvm[1]: Compiling APFloat.cpp for Release+Asserts build clang: TargetInfo.cpp:1778: llvm::Type *GetX86_64ByValArgumentPair(llvm::Type *, llvm::Type *, const llvm::TargetData &): Assertion `Lo->isIntegerTy() && "Invalid/unknown lo type"' failed. 0 clang 0x0000000001c132ef 1 clang 0x0000000001c13804 2 libpthread.so.0 0x00002ba7d7eaec60 3

Duncan, Yes, this is the problem. Running "opt -version" returns: me at here:~/llvm/llvm_core/llvm-2.9$ opt -version Low Level Virtual Machine (http://llvm.org/): llvm version 2.8 (Ubuntu 2.8-0ubuntu1) Optimized build. Built Oct 6 2010 (13:24:23). Host: x86_64-pc-linux-gnu Host CPU: i686 Registered Targets: (none) So, my question is then how do I do a clean

Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: ../llvm_gcc/llvm-gcc-4.2-2.9.source/configure -program-prefix=llvm --enable-llvm=/home/ryan/llvm/llvm_core/llvm-2.9 --enable-languages=c,c++ --disable-jit : (reconfigured) ../llvm_gcc/llvm-gcc-4.2-2.9.source/configure -program-prefix=llvm --enable-llvm=/home/ryan/llvm/llvm_core/llvm-2.9 --enable-languages=c,c++ --disable-jit

I am trying to use ExtractLoop() but I am getting segFaults: 0 opt 0x00000000008edc2f 1 opt 0x00000000008edfda 2 libpthread.so.0 0x00007ffe21203c60 3 opt 0x0000000000895ed9 llvm::Value::getName() const + 9 4 LLVMEXITCDFG.so 0x00007ffe202b80d7 5 opt 0x00000000006fc6e7 llvm::LPPassManager::runOnFunction(llvm::Function&) + 1143 6 opt

Was hoping it might get some help or a better explanation of this: /ADT/APInt.h:1217: uint64_t llvm::APInt::getZExtValue() const: Assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6eb4d05 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64

It looks like this problem only exists on nested loops, ideas? On Thu, Jan 12, 2012 at 11:44 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > Is it not a good idea to try and extract loops that have multiple exits? > > > On Thu, Jan 12, 2012 at 10:44 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > >> I am trying to use ExtractLoop() but I am getting segFaults:

Is it not a good idea to try and extract loops that have multiple exits? On Thu, Jan 12, 2012 at 10:44 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > I am trying to use ExtractLoop() but I am getting segFaults: > > 0 opt 0x00000000008edc2f > 1 opt 0x00000000008edfda > 2 libpthread.so.0 0x00007ffe21203c60 > 3 opt 0x0000000000895ed9

clang: /home/ryan/llvm/llvm_core/llvm-3.0/include/llvm/Support/Casting.h:194: typename cast_retty<PHINode, ilist_iterator<Instruction> >::ret_type llvm::cast(const llvm::ilist_iterator<llvm::Instruction> &): Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed. 0 clang 0x0000000001b3618f 1 clang

On Fri, Nov 16, 2012 at 3:00 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > Was hoping it might get some help or a better explanation of this: > > /ADT/APInt.h:1217: uint64_t llvm::APInt::getZExtValue() const: Assertion > `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed. The error message is exactly what it says: you're trying to call

Has anyone seen this error before? I'm trying to load a pass that apparently isn't registered, it's just the "Hello World" sample , so I don't see the problem. Error: me at here:~/llvm/llvm_core/llvm-2.9$ opt -load Release/lib/LLVMHello.so -hello <cdfg.c> /dev/null Error opening 'Release/lib/LLVMHello.so': Release/lib/LLVMHello.so: undefined symbol: