search for: optzn

...math -funroll-loops -O3 de-gfortran47: /sw/lib/gcc4.7/bin/gfortran -fplugin=/sw/lib/gcc4.7/lib/dragonegg.so -specs=/sw/lib/gcc4.7/lib/integrated-as.specs de-gfortran48: /sw/lib/gcc4.8/bin/gfortran -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs de-gfortran47+optzns: /sw/lib/gcc4.7/bin/gfortran -fplugin=/sw/lib/gcc4.7/lib/dragonegg.so -specs=/sw/lib/gcc4.7/lib/integrated-as.specs -fplugin-arg-dragonegg-enable-gcc-optzns de-gfortran48+optzns: /sw/lib/gcc4.8/bin/gfortran -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs -fpl...

...final!). It would be great > if you could redo the benchmarks rc3. > Duncan, As requested, appended are the updated Polyhedron 2005 benchmark results with both RC1 and RC3 llvm 3.3 testing. There is a small improvement in the dragonegg results (without -fplugin-arg-dragonegg-enable-gcc-optzns) in RC3. I assume we still only have partial coverage of all of the -ffast-math optimizations performed by FSF gcc in llvm's fast-math support, correct? Jack Tested on x86_apple-darwin12 Compile Flags: -ffast-math -funroll-loops -O3 de-gfc47: /sw/lib/gcc4.7/bin/gfortr...

...ted, appended are the updated Polyhedron 2005 benchmark results with both RC1 and RC3 llvm 3.3 testing. thanks for doing this. As rc3 hasn't been tagged yet, I assume you used latest 3.3svn? > There is a small improvement in the dragonegg results (without -fplugin-arg-dragonegg-enable-gcc-optzns) in RC3. I assume > we still only have partial coverage of all of the -ffast-math optimizations performed by FSF gcc in llvm's fast-math > support, correct? These results are very disappointing, I was hoping to see a big improvement somewhere instead of no real improvement anywhere (exc...

Duncan, 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) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize Compile time (seconds) Benchmark A) stock B) gcc 4.5.4/ C) gcc 4.5.4/ gcc 4.5.4 dragonegg/optzns dragonegg ac 0.61 1.65 0.32 aermod 31.24 25.8...

...lease > Thread model: posix > gcc version 4.5.4 20110608 (prerelease) (GCC) > > x86_64 darwin > > 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) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize > D) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize -fplugin-arg-dragonegg-enable-gcc-optzns -fplugin-arg-dragonegg-llvm-ir-optimize=2 > E) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math...

...nks 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) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize > > These numbers really surprised me: the GCC code generators must be really slow > if the entire set of LLVM IR and codegen optimizations takes less time to run > than GCC codegen (since with -fplugin...

Hi guys, According to this patch review: *Title: Remove the '-disable-llvm-passes' flag (which I didn't even know existed, and I suspect many others aren't aware of either) and strength '-disable-llvm-optzns' to do the same thing* Link: https://reviews.llvm.org/D28047 *-disable-llvm-optzns and -disable-llvm-passes are aliasing each other.* *1. Both can be passed to cc1 w/ -Xclang when compilation is run to finish.* E.g [twang15 at c89 temp]$ clang++ -O2 -Xclang -disable-llvm-optzns -save-temps...

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 -fplugin-arg-dragonegg-enable-gcc-optzns is clear on x86_64-apple-darwin10 fo...

...5 --enable-lto --enable-checking=release Thread model: posix gcc version 4.5.4 20110608 (prerelease) (GCC) x86_64 darwin 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) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize D) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize -fplugin-arg-dragonegg-enable-gcc-optzns -fplugin-arg-dragonegg-llvm-ir-optimize=2 E) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-...

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) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize These numbers really surprised me: the GCC code generators must be really slow if the entire set of LLVM IR and codegen optimizations takes less time to run than GCC codegen (since with -fplugin-arg-dragonegg-enable-g...

Current dragonegg svn has all of the -fplugin-arg-dragonegg-enable-gcc-optzns bugs for usage with -ffast-math -O3 addressed except for those related to PR2314. Using the -fno-tree-vectorize option, we can evaluate the current state of -fplugin-arg-dragonegg-enable-gcc-optzns with the Polyhedron 2005 benchmarks compared to stock dragonegg and stock gcc 4.5.4. The runtime ben...

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 gcc 4.5.3svn using the himenoBMTxpa benchmark, > > the enhancement to code performance from -fplugin-arg-dragonegg-enable-gcc-optzns is &gt...

...r: no input files [twang15 at c89 temp]$ clang -mllvm --help clang-5.0: error: no input files Anything wrong? On Tue, Jan 9, 2018 at 1:56 AM, Craig Topper <craig.topper at gmail.com> wrote: > There's a hack in lib/Driver/ToolChains/Clang.cpp to accept "-mllvm > -disable-llvm-optzns" as a hack for legacy compatibility. It's deprecated > and the -Xclang spelling should be used. > > There does appear to be a bug with "-mllvm -disable-llvm-optzns" and > -save-temps. -save-temps causes clang to be invoked separately to text > assembly into binary...

There's a hack in lib/Driver/ToolChains/Clang.cpp to accept "-mllvm -disable-llvm-optzns" as a hack for legacy compatibility. It's deprecated and the -Xclang spelling should be used. There does appear to be a bug with "-mllvm -disable-llvm-optzns" and -save-temps. -save-temps causes clang to be invoked separately to text assembly into binary code, and it looks like...

...in-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 this to find a good choice. Best wishes, Duncan. > Current dragonegg svn has all of the -fplugin-arg-dragonegg-enable-gcc-optzns bugs for > usage with -ffast-math -O3 addressed except for those related to PR2314. Using the -fno-tree-vectorize > option, we can evaluate the current state of -fplugin-arg-dragonegg-enable-gcc-optzns with > the Polyhedron 2005 benchmarks compared to stock dragonegg and stock gcc 4.5.4....

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 -fplugin-arg-dragonegg-enable-gcc-optzns is > clear on x86_...

...-math -funroll-loops -O3 de-gfortran47: /sw/lib/gcc4.7/bin/gfortran -fplugin=/sw/lib/gcc4.7/lib/dragonegg.so -specs=/sw/lib/gcc4.7/lib/integrated-as.specs de-gfortran48: /sw/lib/gcc4.8/bin/gfortran -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs de-gfortran47+optzns: /sw/lib/gcc4.7/bin/gfortran -fplugin=/sw/lib/gcc4.7/lib/dragonegg.so -specs=/sw/lib/gcc4.7/lib/integrated-as.specs -fplugin-arg-dragonegg-enable-gcc-optzns de-gfortran48+optzns: /sw/lib/gcc4.8/bin/gfortran -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs -fpl...

...clang -mllvm --help > clang-5.0: error: no input files > > Anything wrong? > > On Tue, Jan 9, 2018 at 1:56 AM, Craig Topper <craig.topper at gmail.com> > wrote: > >> There's a hack in lib/Driver/ToolChains/Clang.cpp to accept "-mllvm >> -disable-llvm-optzns" as a hack for legacy compatibility. It's deprecated >> and the -Xclang spelling should be used. >> >> There does appear to be a bug with "-mllvm -disable-llvm-optzns" and >> -save-temps. -save-temps causes clang to be invoked separately to text >>...

...5.0: error: no input files >> >> Anything wrong? >> >> On Tue, Jan 9, 2018 at 1:56 AM, Craig Topper <craig.topper at gmail.com> >> wrote: >> >>> There's a hack in lib/Driver/ToolChains/Clang.cpp to accept "-mllvm >>> -disable-llvm-optzns" as a hack for legacy compatibility. It's deprecated >>> and the -Xclang spelling should be used. >>> >>> There does appear to be a bug with "-mllvm -disable-llvm-optzns" and >>> -save-temps. -save-temps causes clang to be invoked separately t...

...nks 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) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize > > These numbers really surprised me: the GCC code generators must be really slow > if the entire set of LLVM IR and codegen optimizations takes less time to run > than GCC codegen (since with -fplugin...