similar to: [LLVMdev] llvm-gcc compile failure on darwin8.8

hello, upgrading llvm-gcc4 from 1.9 release to trunk caused the following build failure for me on darwin: build/genattrtab /Users/ebner/dev/opt/llvm-gcc-svn/gcc/config/i386/ i386.md > tmp-attrtab.c genattrtab: Automaton `ppro_load': Insn `ppro_fmov_XF_load' will never be issued genattrtab: Automaton `ppro_load': Insn `ppro_sse_icvt_SF' will never be issued genattrtab:

Hi, I just updated my LLVM sources from CVS/HEAD and rebuilt them. And I downloaded the GCC4 frontend from the 1.9 release. Now I cannot compile anything, since GCC frontend seems to produce BC files that cannot be read by llvm-dis, llc and other utils. llvm-dis shows a following message: Bytecode formats < 7 are not longer supported. Use llvm-upgrade. (Vers=6, Pos=9) But since the new

On 8/4/06, Anton Korobeynikov <asl at math.spbu.ru> wrote: > > Hello Anton > > Thu, 3 Aug 2006 23:13:52 +0400 you wrote: > > > I won't be available for the next 10-12 hours if you'll need some more > > files. > Well. I have one idea. Could you please execute "sort --version" from > your cygwin shell and let me know, whether it's GNU one

I'm getting a build error when trying to build gcc4 from sources. This is for the recent 1.9 release. How I built llvm-1.9: ----------------------------- tar zxf llvm-1.9.tar.gz cd llvm-1.9/ ./configure --prefix=/custom/llvm-1.9 make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION='-O2' tools-only make install How I built gcc4: ----------------------------- export

I'm having some trouble getting llvm-gcc4 to compile. It's unable to compile darwin-crt3.c. It's mentioning "Complex expression. Absolute segment assumed." but I'm not sure if that's a real error message. Has anyone run into this before? I'm running on a G4 apple 10.4.8, kernel version 8.6.0. I googled around and found a bug with the same error message:

Hi Roman, On Tue, 2006-12-19 at 17:32 -0800, Roman Levenstein wrote: > Hi, > > I just updated my LLVM sources from CVS/HEAD and rebuilt them. And I > downloaded the GCC4 frontend from the 1.9 release. > > Now I cannot compile anything, since GCC frontend seems to produce BC > files that cannot be read by llvm-dis, llc and other utils. > > llvm-dis shows a following

hello, i am new to llvm and can't manage to compile the gcc backend. my steps: i compile the llvm-source first as suggested in "README.LLVM" that works fine and without any issues. then i make a new dir called build. from there i do the following: stefan at ubuntu:~/programs/llvm/build$ ../llvm-gcc4-1.9.source/configure --enable-languages=c,c++ --prefix=/usr/local/

Hello, Aaron. > /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf': > /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://llvm.org/bugs> for instructions. You should: 1. Try to emit bytecode with --emit-llvm compiler switch. 1.1

Hi Stefan, On Thu, 2007-03-01 at 23:26 +0100, Stefan Weigert wrote: > hello, > > i am new to llvm and can't manage to compile the gcc backend. Okay. Did you read: http://llvm.org/docs/GettingStartedGuide.html ? > > my steps: > i compile the llvm-source first as suggested in "README.LLVM" > that works fine and without any issues. Okay. > > then i

Chris, On Sat, 2006-11-25 at 11:39 -0800, Chris Lattner wrote: > On Sat, 25 Nov 2006, Anton Korobeynikov wrote: > > Hello, Matthew. > >> Someone reported this earlier but the situation remains unchanged. > > I'm sorry for delay. Files will be uploaded to LLVM download section > > soon. > > Anton, you have commit access to the web page. Please just check

>> I assume you have an Mac with an Intel processor. > > Yes. Sorry, I forgot to mentioned it in the mailbody. > >> Download this: >> http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz > > I think that is the same tarball I used before. Ok. I'm confused. Do you want llvm-gcc3 or llvm-gcc4? The tarball above is a binary for llvm-gcc4 for Mac x86. You

First, thanks for testing this! > Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) > > HIGH LEVEL COMMENTS > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > that be llvm-1.9? We have always labeled the dir just llvm which is fine. If you build llvm it will know its version 1.9. > * LLVM was built in Release mode

Hi, On Nov 13, 2006, at 9:17 PM, Tanya M. Lattner wrote: > I assume you have an Mac with an Intel processor. Yes. Sorry, I forgot to mentioned it in the mailbody. > Download this: > http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz I think that is the same tarball I used before. > Let me know if that doesn't work. Again: there is no fixheader-script like you

Reid & Aaron > > This is the same error that appears alot of times on the 'make check' > > of the debug build. > > > > What is going on here please ? > > Sounds to me like the llvm-gcc being used wasn't configured using > --with-llvm=. That message occurs when llvm-gcc is built > "normally" (without using llvm). Yes. llvm-gcc4

hi all, i surely overlooked something. but i am currently trying to do some benchmarking stuff with llvm. in my thesis i was using llvm-1.5 (i did some extension work, which i would have to frontport now). But unfortunately 1.5 is for some benchmarks unstable (at least on my box) such that llc sigsegvs sometimes, etc. So I wanted to give 1.9 a go and build that on the my intel mac book. I did

Hello Anton Thu, 3 Aug 2006 12:38:54 +0400 you wrote: > I've updated it yesterday and rebuilt - llvm built fine. But when > building llvm-gcc4 (also updated yesterday from new /trunk > directory) it fails with the same error. You might easily get llvm-gcc4-mingw32 binaries from "prerelease" directory. Since stdcall, fastcall & dllimport stuff is unsupported right now,

On Thu, 16 Nov 2006, Tanya M. Lattner wrote: >> * I don't think this is ready for release. In particular the llvm-gcc4 >> binary >> seg faults on FC 5 for most of llvm-test programs. >> * I'm going to re-try without using the binaries and building >> everything from scratch. > > Does llvm-gcc4 seg fault for make check? I've done extensive

On Nov 14, 2006, at 8:30 AM, Tanya M. Lattner wrote: > >>> I assume you have an Mac with an Intel processor. >> >> Yes. Sorry, I forgot to mentioned it in the mailbody. >> >>> Download this: >>> http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz >> >> I think that is the same tarball I used before. > > Ok. I'm

Hello LLVM-people, I realize most of you have other things on their head now, with the 1.9 release coming up, but I'd like to ask some questions regarding the llvm-gcc frontend. The current llvm-gcc4 frontend is based on GCC 4.0.1, as far as I can tell from the docs. I also understand that GCC 4.1.x will probably be skipped, to go to the upcoming GCC 4.2 release directly (which is

Dale Johannesen wrote: > On Oct 22, 2007, at 2:08 AM, Dietmar Ebner wrote: >> next, i think (one of) the problem(s) is the use of >> [HOST_]WORDS_BIG_ENDIAN instead of [HOST_]FLOAT_WORDS_BIG_ENDIAN in >> llvm-convert.cpp (see patch below). >> >> this fixes single precision floating point but breaks double >> precision. >> for arm-softfloat-linux-gnu,