[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

[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 se

[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 v

[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 degrad

[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 suspec

[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

[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 op

[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

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

2009-11-07 Thread nmm1 at cam dot ac dot uk
ty: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: nmm1 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41977

[Bug other/40104] ARG_MAX erroneously used in upc-4.2.3.6/gcc/upc/upc-cmd.c

2009-05-11 Thread nmm1 at cam dot ac dot uk
--- Comment #2 from nmm1 at cam dot ac dot uk 2009-05-11 17:17 --- I have now found a SECOND set of instructions on how to report a bug in gcc upc. I will copy this to http://www.intrepid.com/upc/bugs.html. Please just cancel this report if this is the wrong place. -- http

[Bug c/40104] New: ARG_MAX erroneously used in upc-4.2.3.6/gcc/upc/upc-cmd.c

2009-05-11 Thread nmm1 at cam dot ac dot uk
at cam dot ac dot uk GCC build triplet: All GCC host triplet: All GCC target triplet: All http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40104

[Bug c/34071] Poor precision of complex division __divdc3 in 64-bit on Intel

2007-11-12 Thread nmm1 at cam dot ac dot uk
--- Comment #5 from nmm1 at cam dot ac dot uk 2007-11-12 18:58 --- To Andrew Pinski: nothing - it was one of the first things I tried. To [EMAIL PROTECTED]: PLEASE don't try to follow Annex G - that is about as broken as it is possible to be; I use it as a horrible example

[Bug c/34071] Poor precision of complex division __divdc3 in 64-bit on Intel

2007-11-12 Thread nmm1 at cam dot ac dot uk
--- Comment #2 from nmm1 at cam dot ac dot uk 2007-11-12 14:25 --- Well, yes and no. I am sorry, but that reply has raised several separate points, so there is a threat of a thread split. 1) It is vaguely related to PR323, yes, but not simply. What I was saying could be considered is

[Bug c/34071] New: Poor behaviour of complex division in 64-bit on Intel

2007-11-12 Thread nmm1 at cam dot ac dot uk
should be small is actually infinite! -- Summary: Poor behaviour of complex division in 64-bit on Intel Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: nmm1 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34071