https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876
Bill Long changed:
What|Removed |Added
Resolution|DUPLICATE |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876
Dominique d'Humieres changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876
--- Comment #8 from Bill Long 2010-12-27 01:42:20 UTC
---
I am out of the office until Monday, January 3, 2011. Send technical questions
to spsl...@cray.com.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876
Daniel Franke changed:
What|Removed |Added
Status|WAITING |NEW
CC|
--- Comment #7 from longb at cray dot com 2010-05-07 22:06 ---
The original problem reported in the Description concerned a missing error
message. So, fixing the segfault (while an excellent situation) does not
address the original issue. My 2 cents is this is not ready to close yet.
--- Comment #6 from dfranke at gcc dot gnu dot org 2010-05-07 19:50 ---
(In reply to comment #5)
> I tried 4.4.2 and do not any longer see the segfault on the Cray XT system.
This PR can thus be closed?
--
dfranke at gcc dot gnu dot org changed:
What|Removed
--- Comment #5 from longb at cray dot com 2009-11-13 22:19 ---
I tried 4.4.2 and do not any longer see the segfault on the Cray XT system. I
suspect this was fixed by addressing the problem noted in Comment #3.
The original problem of not issuing the error message at compile time rema
--- Comment #4 from burnus at gcc dot gnu dot org 2009-07-28 14:43 ---
(In reply to comment #1)
> I certainly can't reproduce any kind of segfault with this.
Neither can I. Regarding both examples (comment 0 and comment 1), ifort 11.1
happily accepts both.
I am not sure whether it is
--- Comment #3 from jv244 at cam dot ac dot uk 2009-07-28 14:34 ---
(In reply to comment #1)
> I certainly can't reproduce any kind of segfault with this.
It could be that it segfaults for Bill because 'ftn' adds -static to the
compiler options, but doesn't link libpthread with '-Wl,--w
--- Comment #2 from longb at cray dot com 2009-07-28 13:47 ---
The text at [75:19-20] of the OpenMP 2.5 standard, May 2008, says:
"Variables that appear in namelist statements, in variable format expressions,
and in Fortran expressions for statement function definitions, may not appear
--- Comment #1 from jakub at gcc dot gnu dot org 2009-07-28 12:20 ---
I certainly can't reproduce any kind of segfault with this.
And, it is unclear to me whether this restriction (why it is there at all,
doesn't make much sense) is meant just for statement functions referenced
within th
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |jakub at gcc dot gnu dot org
|dot org
13 matches
Mail list logo
