similar to: [LLVMdev] dragonegg-2.9 build fail

The new dragonegg 2.9 sources fail to build against either FSF gcc 4.5.2 or 4.5.3svn (with the i386_static.diff patch applied) on x86_64-apple-darwin10. In both cases, the build fails as... GCC=/sw/lib/gcc4.5/bin/gcc-4 LLVM_CONFIG=/sw/bin/llvm-config make CPPFLAGS="-DENABLE_LTO -I/sw/include" Compiling utils/TargetInfo.cpp <command-line>: warning: "__STDC_LIMIT_MACROS"

On Fri, Apr 08, 2011 at 01:58:10PM +0200, Duncan Sands wrote: >> Is there anything I can do to make the build more verbose so I can debug this? > > make VERBOSE=1 Duncan, Oddly this shows... GCC=/sw/lib/gcc4.5/bin/gcc-4 LLVM_CONFIG=/sw/bin/llvm-config make VERBOSE=1 CPPFLAGS="-DENABLE_LTO -I/sw/include" Compiling utils/TargetInfo.cpp g++ -c

Looks like that break came from http://llvm.org/viewvc/llvm-project?view=rev&revision=135154 Judging by this<http://llvm.org/docs/doxygen/html/classllvm_1_1ArrayRef.html#a3b1f44186f9787d7ffacb54b62d6798c> ArrayRef ctor you should be able to simplify those calls by changing the last two arguments from "&foo, 1" to, simply, "foo". On Mon, Jul 18, 2011 at 6:59 AM,

Despite the commit of... ------------------------------------------------------------------------ r135371 | lattner | 2011-07-18 00:25:32 -0400 (Mon, 18 Jul 2011) | 2 lines untested patch to de-constify llvm::Type, patch by David Blaikie! current dragonegg svn at r135391 still fails to compile against FSF gcc 4.5.3 with the failure... In file included from

On Sun, Apr 11, 2010 at 10:29:28AM +0200, Duncan Sands wrote: > Hi Jack, > >> bash-3.2$ GCC=/sw/bin/gcc-4 CC=gcc-4 CXX=g++-4 CFLAGS=-I/sw/include CXXFLAGS=-I/sw/include LLVM_CONFIG=/sw/lib/llvm/bin/llvm-config make >> g++-4 -c -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -MD -MP -DIN_GCC -DREVISION=\"100954M\"

On Sat, Apr 10, 2010 at 08:29:07PM -0500, Peter O'Gorman wrote: > On 04/10/2010 08:01 PM, Jack Howarth wrote: > > > > > bash-3.2$ GCC=/sw/bin/gcc-4 CC=gcc-4 CXX=g++-4 CFLAGS=-I/sw/include CXXFLAGS=-I/sw/include LLVM_CONFIG=/sw/lib/llvm/bin/llvm-config make > > g++-4 -c -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -MD

Hi Jack, > bash-3.2$ GCC=/sw/bin/gcc-4 CC=gcc-4 CXX=g++-4 CFLAGS=-I/sw/include CXXFLAGS=-I/sw/include LLVM_CONFIG=/sw/lib/llvm/bin/llvm-config make > g++-4 -c -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -MD -MP -DIN_GCC -DREVISION=\"100954M\" -DTARGET_NAME=\"x86_64-apple-darwin10.3.0\" -I/Users/howarth/llvm_svn/dragonegg

On 04/10/2010 08:01 PM, Jack Howarth wrote: > > bash-3.2$ GCC=/sw/bin/gcc-4 CC=gcc-4 CXX=g++-4 CFLAGS=-I/sw/include CXXFLAGS=-I/sw/include LLVM_CONFIG=/sw/lib/llvm/bin/llvm-config make > g++-4 -c -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -MD -MP -DIN_GCC -DREVISION=\"100954M\"

On Sat, Apr 10, 2010 at 01:52:18PM +0200, Duncan Sands wrote: > Hi Jack, > > > Is anyone building dragon-egg on darwin? > > Anton built it once. There were some problems with dynamic libraries: gcc's > plugin support requires the use of dynamic libraries, and the configure logic > it uses thinks that darwin does not support dynamic libraries! So it is >

Duncan, Here are the complete benchmarks rerun against gcc 4.5.4 built with... Using built-in specs. COLLECT_GCC=gfortran-fsf-4.5 COLLECT_LTO_WRAPPER=/sw/lib/gcc4.5/libexec/gcc/x86_64-apple-darwin11.0.0/4.5.4/lto-wrapper Target: x86_64-apple-darwin11.0.0 Configured with: ../gcc-4.5.4/configure --prefix=/sw --prefix=/sw/lib/gcc4.5 --mandir=/sw/share/man --infodir=/sw/lib/gcc4.5/info

On Thu, Jun 09, 2011 at 08:47:26PM -0400, Jack Howarth wrote: > Duncan, > Here are the complete benchmarks rerun against gcc 4.5.4 built with... > > Using built-in specs. > COLLECT_GCC=gfortran-fsf-4.5 > COLLECT_LTO_WRAPPER=/sw/lib/gcc4.5/libexec/gcc/x86_64-apple-darwin11.0.0/4.5.4/lto-wrapper > Target: x86_64-apple-darwin11.0.0 > Configured with:

Hi Jack, > Is anyone building dragon-egg on darwin? Anton built it once. There were some problems with dynamic libraries: gcc's plugin support requires the use of dynamic libraries, and the configure logic it uses thinks that darwin does not support dynamic libraries! So it is possible that plugin support was automatically disabled because of this. Try configuring with

Hi Jack, I didn't get this error. Could you try again? Is it one of the release candidates in particular that's failing? -bw On Oct 2, 2010, at 8:04 AM, Jack Howarth wrote: > Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. > > #!/bin/bash -ev > export LD=`xcode-select -print-path`/usr/bin/ld > xcode-select -print-path > ulimit -s

On Sat, Apr 09, 2011 at 08:56:49AM -0600, Marcus G. Daniels wrote: > On 4/9/2011 6:09 AM, Duncan Sands wrote: > > Hi Jack, thanks for the numbers. Any chance of analysing why gcc does better on > > those where it does much better than dragonegg? > > > > Ciao, Duncan. > Also, does -fplugin-arg-dragonegg-enable-gcc-optzns get Dragonegg to > match GCC performance

On Fri, Apr 08, 2011 at 07:37:39AM -0400, Jack Howarth wrote: > On Fri, Apr 08, 2011 at 08:28:27AM +0200, Duncan Sands wrote: > > Hi Jack, > > > > > The new dragonegg 2.9 sources fail to build against either FSF gcc 4.5.2 or 4.5.3svn > > > (with the i386_static.diff patch applied) on x86_64-apple-darwin10. In both cases, the > > > build fails as...

Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. #!/bin/bash -ev export LD=`xcode-select -print-path`/usr/bin/ld xcode-select -print-path ulimit -s `ulimit -s` ulimit -s mv ../clang-2.8 ./tools/clang mkdir ../llvm_objdir cd ../llvm_objdir ../llvm-2.8/configure --prefix=/sw --prefix=/sw --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw

In trying to package up LLVM for Debian, it appears that x86_64 is no longer a supported architecture -- so, my first question is, is that correct? Best I can tell, the only thing that's supposed to work for x86_64 is the C backend. For Debian, I need to build everything from scratch. When trying to build llvm-gcc4 from source, though, I get part way through the build and am told that

On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias Grosser wrote: > On 10/20/2012 05:38 PM, Jack Howarth wrote: >> Duncan, >> Is the documentation for using Polly support in dragonegg correct? I built llvm/polly/dragonegg >> using the documentation at http://polly.llvm.org/example_load_Polly_into_dragonegg.html >> with... >> >> GCC=/sw/lib/gcc4.7/bin/gcc-4

On Fri, Sep 18, 2009 at 11:13:52AM -0700, Nick Kledzik wrote: > > The important thing is that only one unwinder is used. The > _Unwind_Context data structure is different between the darwin and FSF > implementations, so you can't pass it between two different > implementations. Since darwin uses two-level namespace and swapping in > a new libgcc_s.dylib at runtime

There seems to be a bunch of code for making certain that gcc still works even if --enable-gcc isn't used, so I'm assuming that it's at least supposed to be a supported configuration, and hence this issue that I found should probably be looked at: If you compile llvm-gcc-4.2 _without_ --enable-gcc, and then try to compile the following program, you get a rather nasty RTL error.