similar to: [LLVMdev] new dragonegg 3.4 warning on darwin12

On Thu, Nov 21, 2013 at 07:37:46PM -0500, Jack Howarth wrote: > Duncan, > Is this expected for x86_64-apple-darwin12 under Xcode 5? Using current > llvm/compiler-rt/clang/polly/testsuite with dragonegg 3.4 branch, I see > the warnings... > > % /sw/lib/gcc4.8/bin/gcc-4 -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs

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 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 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config ENABLE_LLVM_PLUGINS=1 make

Hi, > I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: > > dyld: fast lazy bind offset out of range (53437, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 > > means the initializer

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 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config ENABLE_LLVM_PLUGINS=1 make CPPFLAGS="-DENABLE_LTO -I/sw/include" The resulting dragonegg plugin works fine

On Tue, Oct 23, 2012 at 09:41:46AM +0200, Duncan Sands wrote: > Hi, > >> I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: >> >> dyld: fast lazy bind offset out of range (53437, max=7640) in image

Hi Jack, On 29/05/13 22:04, Jack Howarth wrote: > On Wed, May 29, 2013 at 03:25:30PM +0200, Duncan Sands wrote: >> Hi Jack, I pulled the loop vectorizer and fast math changes into the 3.3 branch, >> so hopefully they will be part of 3.3 rc3 (and 3.3 final!). It would be great >> if you could redo the benchmarks rc3. >> > > Duncan, > As requested, appended

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 http://llvm.org/bugs/show_bug.cgi?id=15980 which results in unresolved symbols for _iround and _iroundf in the aermod and rnflow testcases. Note that this

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

On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote: > 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

On 10/21/2012 10:57 AM, Jack Howarth wrote: > On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote: >> 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

Hi Jack, thanks for splitting out what the effects of LLVM's / GCC's vectorizers is. On 01/06/13 21:34, Jack Howarth wrote: > On Sat, Jun 01, 2013 at 06:45:48AM +0200, Duncan Sands wrote: >> >> These results are very disappointing, I was hoping to see a big improvement >> somewhere instead of no real improvement anywhere (except for gas_dyn) or a >> regression

On Sun, Oct 21, 2012 at 11:01:37AM -0700, Tobias Grosser wrote: > On 10/21/2012 10:57 AM, Jack Howarth wrote: >> On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote: >>> 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:

On Sat, Jun 01, 2013 at 06:45:48AM +0200, Duncan Sands wrote: > > These results are very disappointing, I was hoping to see a big improvement > somewhere instead of no real improvement anywhere (except for gas_dyn) or a > regression (eg: mdbx). I think LLVM now has a reasonable array of fast-math > optimizations. I will try to find time to poke at gas_dyn and induct: since >

Duncan, With r182593, the dragonegg 3.3 branch now completely passes the Polyhedron 2005 benchmarks using the FSF gcc 4.8.1svn compiler. Thanks. Jack Tested on x86_apple-darwin12 Compile Flags: -ffast-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:

Jack, I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: dyld: fast lazy bind offset out of range (53437, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 means the initializer called something which

On Sun, Oct 21, 2012 at 02:35:49PM -0400, Jack Howarth wrote: > On Sun, Oct 21, 2012 at 11:01:37AM -0700, Tobias Grosser wrote: > > On 10/21/2012 10:57 AM, Jack Howarth wrote: > >> On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote: > >>> On 10/21/2012 09:13 AM, Jack Howarth wrote: > >>>> On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias

On Wed, May 29, 2013 at 03:25:30PM +0200, Duncan Sands wrote: > Hi Jack, I pulled the loop vectorizer and fast math changes into the 3.3 branch, > so hopefully they will be part of 3.3 rc3 (and 3.3 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

Jack, Can you please file a bug report and attach the BC files for the major loops that we miss ? Thanks, Nadav On Jun 2, 2013, at 1:27, Duncan Sands <duncan.sands at gmail.com> wrote: > Hi Jack, thanks for splitting out what the effects of LLVM's / GCC's vectorizers > is. > > On 01/06/13 21:34, Jack Howarth wrote: >> On Sat, Jun 01, 2013 at 06:45:48AM +0200,

Actually this kind of opportunities, as outlined bellow, was one of my contrived motivating example for fast-math. But last year we don't see such opportunities in real applications we care about. t1 = x1/y ... t2 = x2/y. I think it is better to be taken care by GVN/PRE -- blindly convert x/y => x *1/y is not necessarily beneficial. Or maybe we can blindly perform such