similar to: [LLVMdev] dragonegg bootstrap gcc 4.5.2

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] dragonegg bootstrap gcc 4.5.2"

2011 Apr 19
0
[LLVMdev] dragonegg bootstrap gcc 4.5.2
On Apr 19, 2011, at 6:59 AM, Jack Howarth wrote: > The current dragonegg trunk svn used under FSF gcc 4.5.2 with llvm 2.9 > is able to bootstrap FSF gcc 4.5.2 itself on x86_64-apple-darwin10... > > Using built-in specs. > COLLECT_GCC=gcc-mp-4.5 > COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin10/4.5.2/lto-wrapper > Target: x86_64-apple-darwin10 >
2011 Apr 08
5
[LLVMdev] dragonegg build failure
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"
2011 Apr 15
1
[LLVMdev] -fplugin-arg-dragonegg-enable-gcc-optzns impact
On Fri, Apr 15, 2011 at 08:53:19AM +0200, Duncan Sands wrote: > Hi Jack, > > > Now that dragoneegg is robust in its default usage and the dragonegg svn > > is moderately stable with -fplugin-arg-dragonegg-enable-gcc-optzns, it is > > possible to gauge the impact of that feature. Comparing clang 2.9, FSF gcc 4.5.3svn, > > FSF gcc 4.6.0 and dragonegg svn with FSF
2011 Apr 15
2
[LLVMdev] -fplugin-arg-dragonegg-enable-gcc-optzns impact
Now that dragoneegg is robust in its default usage and the dragonegg svn is moderately stable with -fplugin-arg-dragonegg-enable-gcc-optzns, it is possible to gauge the impact of that feature. Comparing clang 2.9, FSF gcc 4.5.3svn, FSF gcc 4.6.0 and dragonegg svn with FSF gcc 4.5.3svn using the himenoBMTxpa benchmark, the enhancement to code performance from
2011 Apr 15
0
[LLVMdev] -fplugin-arg-dragonegg-enable-gcc-optzns impact
Hi Jack, > Now that dragoneegg is robust in its default usage and the dragonegg svn > is moderately stable with -fplugin-arg-dragonegg-enable-gcc-optzns, it is > possible to gauge the impact of that feature. Comparing clang 2.9, FSF gcc 4.5.3svn, > FSF gcc 4.6.0 and dragonegg svn with FSF gcc 4.5.3svn using the himenoBMTxpa benchmark, > the enhancement to code performance from
2011 Apr 08
3
[LLVMdev] dragonegg build failure
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... > > what does the command > ./TargetInfo -p > return (the TargetInfo program
2011 Jul 18
5
[LLVMdev] dragonegg svn still broken
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
2011 Apr 08
0
[LLVMdev] dragonegg build failure
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...
2011 Apr 08
0
[LLVMdev] dragonegg build failure
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... what does the command ./TargetInfo -p return (the TargetInfo program is created during the dragonegg build). Some of your errors are consistent with this program failing to run.
2011 Apr 08
2
[LLVMdev] dragonegg build failure
Hi ether, how did you build it exactly? I logged into gcc16 and tried to reproduce. But I get /home/ether/local/gcc-4.5/lib/gcc/x86_64-unknown-linux-gnu/4.5.3/plugin/include/real.h:28:17: error: mpc.h: No such file or directory In file included from /home/ether/local/gcc-4.5/lib/gcc/x86_64-unknown-linux-gnu/4.5.3/plugin/include/rtl.h:28, from
2011 Apr 08
0
[LLVMdev] dragonegg build failure
hi, On Fri, Apr 8, 2011 at 8:38 AM, Jack Howarth <howarth at bromo.med.uc.edu> wrote: >   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... Dragonegg revision 129116 also fail on x86_64 linux, with gcc-4.5 revision 172158, i got:
2011 Apr 08
0
[LLVMdev] dragonegg build failure
hi Duncan, i install mpc-0.8.2 in /home/ether/local/, and gcc-4.5 is configure with: $HOME/sources/gcc-4.5/configure --enable-plugin --enable-lto --prefix=$HOME/local/gcc-4.5/ --enable-languages=c,c++ --disable-bootstrap --disable-multilib --with-mpc=$HOME/local --with-libelf=$HOME/local On Sat, Apr 9, 2011 at 12:00 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi ether, how did you
2011 Jul 19
0
[LLVMdev] dragonegg svn still broken
On Tue, Jul 19, 2011 at 10:12:47AM +0100, Jay Foad wrote: > On 18 July 2011 15:23, David Blaikie <dblaikie at gmail.com> wrote: > > Looks like that break came > > from http://llvm.org/viewvc/llvm-project?view=rev&revision=135154 > > Judging by this ArrayRef ctor you should be able to simplify those calls by > > changing the last two arguments from
2011 Apr 08
4
[LLVMdev] dragonegg build failure
Hi ether, > i install mpc-0.8.2 in /home/ether/local/, and gcc-4.5 is configure with: > $HOME/sources/gcc-4.5/configure --enable-plugin --enable-lto > --prefix=$HOME/local/gcc-4.5/ --enable-languages=c,c++ > --disable-bootstrap --disable-multilib --with-mpc=$HOME/local > --with-libelf=$HOME/local because GCC headers include mpc.h, when dragonegg uses GCC headers then it needs to
2011 Mar 22
4
[LLVMdev] -emit-llvm on ubuntu is broken
Hi Eric, here is my -emit-llvm -S -v output: Using built-in specs. COLLECT_GCC=gcc-4.5 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.1-7ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
2011 Apr 08
0
[LLVMdev] dragonegg build failure
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
2010 Apr 10
0
[LLVMdev] darwin dragon-egg build issues
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
2011 Apr 08
4
[LLVMdev] dragonegg build failure
> Is there anything I can do to make the build more verbose so I can debug this? make VERBOSE=1
2010 Aug 24
4
[LLVMdev] dragonegg plugin invoking issue
Hi, I am using latest sources on GCC (gcc4.5_branch), LLVM and dragonegg. I am able to build all three bits though unsuccessfull in building. Already done obvious things - checked out the sources as per defined in "Getting the development version" on dragonegg.llvm.org - Modified the llvm-backend.cpp in dragonegg to make available the global plugin_is_GPL_compatible publically -
2011 Jul 18
0
[LLVMdev] dragonegg svn still broken
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,