[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-10 Thread nmm1 at cam dot ac dot uk
--- Comment #15 from nmm1 at cam dot ac dot uk 2009-11-10 21:49 --- It's come back again. The more that it does that, the more that I am convinced that it is something horrible in thread management, perhaps a symbol clash, race condition or overwriting, and the root cause might well not

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-11-10 20:30 --- Marking status as waiting. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-10 Thread nmm1 at cam dot ac dot uk
--- Comment #13 from nmm1 at cam dot ac dot uk 2009-11-10 13:32 --- Oh, joy. This went soft yesterday, and today I can't repeat the effects. I have some of the evidence in Email I sent to the ACML expert, who has managed to repeat them at least once. But, at BEST, the effects seem to d

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #12 from nmm1 at cam dot ac dot uk 2009-11-07 23:33 --- Subject: Re: gfortran -fopenp and ACML_MP seem incompatible On Nov 7 2009, burnus at gcc dot gnu dot org wrote: > > --- Comment #11 from burnus at gcc dot gnu dot org 2009-11-07 22:19 > --- Which version of AC

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread burnus at gcc dot gnu dot org
--- Comment #11 from burnus at gcc dot gnu dot org 2009-11-07 22:19 --- Which version of ACML are you using? I get a bit confused with all those 4-dot-something version numbers as both GCC and ACML have them. Do you use ACML 4.3.0? strings /opt/acml4.3.0/gfortran64/lib/libacml.a |grep

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #10 from nmm1 at cam dot ac dot uk 2009-11-07 19:15 --- Subject: Re: gfortran -fopenp and ACML_MP seem incompatible On Nov 7 2009, kargl at gcc dot gnu dot org wrote: > >OpenMP clearly helps the 'Coded Cholesky time', but it >causes a factor of 10 degradation in the 'Coded

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread kargl at gcc dot gnu dot org
--- Comment #9 from kargl at gcc dot gnu dot org 2009-11-07 19:00 --- Even without acml, there appears to be an issue. gfortran44 -o one -O2 -pipe -march=native one.f90 -L/usr/local/lib \ -llapack -lblas -fopenmp ./one fred_f_1000 LAPACK Cholesky time = .27 seconds, CPU = .27

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #8 from nmm1 at cam dot ac dot uk 2009-11-07 18:56 --- Subject: Re: gfortran -fopenp and ACML_MP seem incompatible On Nov 7 2009, rguenth at gcc dot gnu dot org wrote: > > --- Comment #7 from rguenth at gcc dot gnu dot org 2009-11-07 18:40 > --- I suspect acml_mp i

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread rguenth at gcc dot gnu dot org
--- Comment #7 from rguenth at gcc dot gnu dot org 2009-11-07 18:40 --- I suspect acml_mp is built using a different GCC version and they link libgomp statically. Can you check what the acml_mp library links against? Just use ldd for this. Then check that this is consistent with what y

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #6 from nmm1 at cam dot ac dot uk 2009-11-07 18:29 --- Subject: Re: gfortran -fopenp and ACML_MP seem incompatible No, but I will try to find it. It is definitely a closed source library, and was written by NAG for AMD under contract. I quite agree that the bug could be a

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread kargl at gcc dot gnu dot org
--- Comment #5 from kargl at gcc dot gnu dot org 2009-11-07 18:24 --- Nick, Have you also reported this issue to the ACML forum? AFAICT, acml is a closed source library (at least I couldn't find the source code), and the problem may in fact be within acml. -- http://gcc.gnu.org/bu

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #4 from nmm1 at cam dot ac dot uk 2009-11-07 17:48 --- Sorry - there's no need to send you the data file - I can send the programs I use to generate it, which are very short. I have done so. To run these, compile them into binaries of the same name with almost any options,

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #3 from nmm1 at cam dot ac dot uk 2009-11-07 17:46 --- Created an attachment (id=18990) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18990&action=view) The second half of the generation code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41977

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #2 from nmm1 at cam dot ac dot uk 2009-11-07 17:46 --- Created an attachment (id=18989) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18989&action=view) The first half of the data generation code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41977

[Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible

2009-11-07 Thread nmm1 at cam dot ac dot uk
--- Comment #1 from nmm1 at cam dot ac dot uk 2009-11-07 17:44 --- Created an attachment (id=18988) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18988&action=view) The source of the failing program -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41977