similar to: [LLVMdev] 2.1 Pre-Release Available (testers needed)

LLVM-GCC 4.0 fails on Cygwin, possibly due to lack of symbolic links. Configuring in i686-pc-cygwin/libstdc++-v3 configure: creating cache ./config.cache checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking target system type... i686-pc-cygwin checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes

> LLVM-GCC 4.0 fails on Cygwin, possibly due to lack of symbolic links. I am trying with llvm-gcc-4.2 from svn. Aaron

I am getting an "--emit-llvm is not supported in this configuration" error on a release build on Cygwin, the debug build is fine. make[3]: Entering directory `/usr/build/llvm/runtime/GCCLibraries/libc' llvm[3]: Compiling atox.c for Release build (bytecode) llvm-gcc: --emit-llvm is not supported in this configuration. make[3]: ***

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

Tanya Lattner wrote: > LLVMers, > > The 2.1 pre-release (version 1) is available for testing: > http://llvm.org/prereleases/2.1/version1/ A couple months ago, I had a problem packaging llvm-gcc for macports because one of the binaries from llvm-gcc was somehow getting used by Apple's gcc driver instead of the native one. This was causing some subtle bugs for people. Anyway,

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM

On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,

> For the windows sub-target is it safe to assume Microsoft's linker is the being targeted? I'd really appreciate if both ms link and gnu ld will be tested, if this is possible. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 right near the end of compiling llvm-gcc in valarray-inst.cc. assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow scaling by ESP" Does this build on Linux ? My remote Linux box has died and not a ble to reset it for a day or two. /home/ang/build/llvm-gcc/./gcc/xgcc -shared-libgcc

Hello, Aaron. > This is still at the stage of using xgcc.exe AFAICT before any LLVM bytecode > generation. Yep. But xgcc generates code via LLVM! So, you can just copy command line from your terminal, add -emit-llvm, run it and you'll see, that resulting .o will be LLVM bytecode (or won't if FE will crash). > __eprintf is a very simple function so I do not know what could be

I am getting an error building svn llvm-gcc on Cygwin :- /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ -B/usr/llv m-gcc/i686-pc-cygwin/bin/ -B/usr/llvm-gcc/i686-pc-cygwin/lib/ -isystem /usr/llvm -gcc/i686-pc-cygwin/include -isystem /usr/llvm-gcc/i686-pc-cygwin/sys-include - O2 -I/home/ang/svn/llvm-gcc/gcc/../winsup/w32api/include -O2 -g -O2 -DIN_GCC -W -Wall

I am getting an assertion firing while building TOT llvm-gcc on Cygwin in libgcc2.c :- /home/ang/build/llvm-gcc/./gcc/xgcc -B/home/ang/build/llvm-gcc/./gcc/ -B/home/an g/llvm-gcc/i686-pc-cygwin/bin/ -B/home/ang/llvm-gcc/i686-pc-cygwin/lib/ -isystem /home/ang/llvm-gcc/i686-pc-cygwin/include -isystem /home/ang/llvm-gcc/i686-pc-c ygwin/sys-include -O2

Hello, Emil > Should I take this (and the other crashes?) off the list and start > filing bugs or something? The transcript looks very "bad" for me. For example: while running: /home/emil/ll/prefix/bin/llvm-gcc -emit-llvm -O3 -S -o - /home/emil/ll/llvm-2.1/test/CFrontend/2007-09-12-PragmaPack.c | grep {26} /home/emil/ll/llvm-2.1/test/CFrontend/2007-09-12-PragmaPack.c:5: warning:

Emil, > # of expected passes 2243 > # of unexpected failures 7 > # of expected failures 5 Could you please provide a log here? It's interesting to see, what is failing now. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Aaron. You wrote Sunday, April 30, 2006, 12:01:10 AM: AG> The Cygwin LLVM release (OPTIMIZED_ENABLED) version triggers a bug in LD AG> (BFD binutils) this may well be common to MinGW as well. Seems so, since debug version of llc.exe builds smoothly. Do you have more information about this issue? -- With best regards, Anton mailto:asl at math.spbu.ru

On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > > Actually its [configure-stage3-intl] where its hanging. > > This can easily be due to inline FP math in the stdlib headers. For example > - I had to maintain slightly hacked mingw32 headers which do not contain > inline FP assembler, otherwise at least libstdc++ configure would

This looks like pr4572. Evan On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote: > I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 > right near the end of compiling llvm-gcc in valarray-inst.cc. > > assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow > scaling by ESP" > > Does this build on Linux ? > > My

> > Actually its [configure-stage3-intl] where its hanging. This can easily be due to inline FP math in the stdlib headers. For example - I had to maintain slightly hacked mingw32 headers which do not contain inline FP assembler, otherwise at least libstdc++ configure would hang. No idea about cygwin though. --- With best regards, Anton Korobeynikov Faculty of Mathematics and

> Also, it would be really nice if an official > cygwin build (the binary) was published too. I spent quite a bit of > time screwing with it a few months ago, and it was quite a bastard to > get going... I had quite a time with it too, could only get the debug version to build as there seemed to be an internal problem with ld. I would very interested in how you got it running and

Hi Aaron, Which revision are you building? Assuming TOT, it's possible this is a bug that I introduced/triggered with the name changes. I know nothing of the status of cygwin however, can you confirm that this used to work? If you use r77097, does it work? - Daniel On Sun, Jul 26, 2009 at 4:23 AM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > I am getting an error