similar to: [LLVMdev] Passing Parameters to LLVM-llc through DragonEgg-3.3

Hi Martin, > thanks for the quick reply. I understand, that the generated code is different > between the two approaches. > But I would still expect IEEE rules to be respected in any case. I do not see > any reason why -fPIC -fomit-frame-pointer > and the like should have any impact on the results computed by the generated code. probably in the direct case you are using the x86

Hi Martin, > I tried using dragonegg to compile some numerical software of ours. I > tried out two different approaches expecting both would yield the same > results: > 1. gfortran-4.6 -fplugin=dragonegg-3.0 -o test.o test.f (I ommitted a > bunch of additional arguments for brevity) > 2. gfortran-4.6 -fplugin=dragonegg-3.0 -fplugin-arg-dragonegg-emit-ir -S > -o test.ll

Hi all, I tried using dragonegg to compile some numerical software of ours. I tried out two different approaches expecting both would yield the same results: 1. gfortran-4.6 -fplugin=dragonegg-3.0 -o test.o test.f (I ommitted a bunch of additional arguments for brevity) 2. gfortran-4.6 -fplugin=dragonegg-3.0 -fplugin-arg-dragonegg-emit-ir -S -o test.ll test.f llc -O0 -o test.s test.ll as

Good evening, guys! I have built dragonegg.dll on cygwin and it works (it seems). I have not tried stage2 build yet. It would be applicable to also mingw32-gcc to enhance gcc/plugin.c. ...Takumi [Instructions] 1. Apply two patches. one is for gcc/config/i386/i386.c. --- a/gcc/configure +++ b/gcc/configure @@ -25621,6 +25621,9 @@ rm -f core conftest.err conftest.$ac_objext \ fi

Hi Duncan, thanks for the quick reply. I understand, that the generated code is different between the two approaches. But I would still expect IEEE rules to be respected in any case. I do not see any reason why -fPIC -fomit-frame-pointer and the like should have any impact on the results computed by the generated code. Are there any options I can set on the command line of llc to force the

On Tue, Apr 03, 2012 at 08:33:33AM -0500, Hal Finkel wrote: > On Tue, 3 Apr 2012 08:57:51 -0400 > Jack Howarth <howarth at bromo.med.uc.edu> wrote: > > > On Tue, Apr 03, 2012 at 09:26:38AM +0200, Duncan Sands wrote: > > > Hi Jack, > > > > > >> Attached are the Polyhedron 2005 benchmark results for current > > >> llvm/dragonegg svn

Hello All, Another newbie question. I am confused as to what options will work with "fplugin-arg-dragonegg-llvm-option" for dragonegg plugin. Readme says it is used to pass command-line options to llvm. I shall consolidate into 3 questions. For all examples below, I used combo- gcc 4.6 + dragonegg(trunk) + llvm(trunk) (1). Does 'fplugin-arg-dragonegg-llvm-option' allow all

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, I have figured out a way to achieve similar effects. gcc -S -c -O0 -fplugin=$(DRAGONEGG_SO) -fplugin-arg-dragonegg-emit-ir hello.c -o hello.bc opt -O3 -disable-simplify-libcalls hello.bc -o hello.bc On Wed, Apr 10, 2013 at 12:54 PM, Jeff Jia <fjia at cs.ucsd.edu> wrote: > Hi chenwj, > > Thanks! I have tried it, but the generated byte code still uses >

Hello All, Another newbie question. I am confused as to what options will work with "fplugin-arg-dragonegg-llvm-option" for dragonegg plugin. Readme says it is used to pass command-line options to llvm. I shall consolidate into 3 questions. For all examples below, I used combo- gcc 4.6 + dragonegg(trunk) + llvm(trunk) (1). Does 'fplugin-arg-dragonegg-llvm-option' allow all

On Wed, Apr 04, 2012 at 05:00:05PM +0200, Duncan Sands wrote: > Hi Jack, > >> Duncan, any idea how to work around that for passing -bb-vectorize-req-chain-depth=3? > > it is being rejected by GCC's plugin options parser. I just implemented a hack > in dragonegg in which colons will be morphed into equals signs. So you should > now be able to pass

Attached are the Polyhedron 2005 benchmark results for current llvm/dragonegg svn on x86_64-apple-darwin11 built against Xcode 4.3.2 and FSF gcc 4.6.3. The benchmarks for -msse3 and -msse4 appear identical (at least for degg+optnz). This is fortunate since there seems to be a bug in -msse4 on 2.33 GHz (T7600) Intel Core 2 Duo Merom (http://llvm.org/bugs/show_bug.cgi?id=12434). I've added two

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

On Thu, Jun 09, 2011 at 03:44:40PM +0200, Duncan Sands wrote: > Hi Jack, thanks for doing this. > >> Below are the tabulated compile times and executable sizes. >> >> A) gcc 4.5.4svn using -msse3 -ffast-math -O3 -fno-tree-vectorize >> B) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize -fplugin-arg-dragonegg-enable-gcc-optzns >> C)

hi, I have dragonegg r131864, gcc-4.5 r174052 and llvm r131897. When i tried to make the llvm test-suite, i got a error message: /home/ether/local/gcc-4.5/bin/gcc -fplugin=/home/ether/sources/dragonegg/dragonegg.so -I/home/ether/build/llvm-ts/projects/test-suite/SingleSource/UnitTests/Vector/SSE -I/home/ether/sources/llvm/projects/test-suite/SingleSource/UnitTests/Vector/SSE

On Thu, May 23, 2013 at 03:40:00PM +0200, Duncan Sands wrote: > Hi Jack, > > On 23/05/13 15:37, Jack Howarth wrote: >> Below are the results for the Polyhedron 2005 benchmarks compiled with llvm/compiler-rt/dragonegg 3.3svn at r182439 against current >> FSF gcc 4.7.3svn and 4.8.1svn. The only major bug remaining in the dragonegg 3.3svn support for gcc 4.8.x is

On 11/12/2010 12:11 PM, Duncan Sands wrote: > Hi Tobias, > >> I committed an extended version of that patch to llvm core and the >> test suite. >> Can you have a look, if it works for you. > > if I configure like this then the configure script thinks llvm-gcc is not > dragonegg: > > configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so" >

Hi Tobias, > I committed an extended version of that patch to llvm core and the test suite. > Can you have a look, if it works for you. if I configure like this then the configure script thinks llvm-gcc is not dragonegg: configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so" --with-llvmgxx="g++-4.5 -fplugin=path/dragonegg.so" There are several reasons for

Hi Jack, thanks for these numbers. Can you also please measure compile times? I'm thinking of enabling gcc optimizations by default, but I don't want to increase compile times, which means choosing a value for the -fplugin-arg-dragonegg-llvm-ir-optimize option that is low enough to get good compile times, yet high enough to get fast code. It would be great if you could play around with

On 10/21/2012 09:13 AM, Jack Howarth wrote: > 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