https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
kugan at gcc dot gnu.org changed:
What|Removed |Added
CC||kugan at gcc dot gnu.org
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Jerry DeLisle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #15 from Jerry DeLisle ---
Author: jvdelisle
Date: Wed Sep 20 01:32:59 2017
New Revision: 252992
URL: https://gcc.gnu.org/viewcvs?rev=252992&root=gcc&view=rev
Log:
2017-09-19 Jerry DeLisle
Backport from trunk
PR l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #14 from Aldy Hernandez ---
Author: aldyh
Date: Wed Sep 13 17:31:53 2017
New Revision: 252585
URL: https://gcc.gnu.org/viewcvs?rev=252585&root=gcc&view=rev
Log:
2017-08-27 Jerry DeLisle
PR libgfortran/78387
* io/l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #13 from Jerry DeLisle ---
Author: jvdelisle
Date: Mon Aug 28 03:42:47 2017
New Revision: 251374
URL: https://gcc.gnu.org/viewcvs?rev=251374&root=gcc&view=rev
Log:
2017-08-27 Jerry DeLisle
PR libgfortran/78387
* i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #12 from Jerry DeLisle ---
Patch submitted here:
https://gcc.gnu.org/ml/fortran/2017-08/msg00045.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #11 from Jerry DeLisle ---
After thinking about this, I think I have a better idea which gets rid of the
stash completely and will avoid allocating a unit structure for internal units.
To accomplish this, I intend to pass the string,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #10 from Jim Wilson ---
newunit_stack needs to be allocated dynamically, just like the newunits array.
I modified libgfortran to compute the highest value of newunit_tos, and print
it when the program exits. I set NEWUNIT_STACK_SIZE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #9 from Dominique d'Humieres ---
Related to pr81195 and pr81241? Works on darwin with 8 threads.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Jerry DeLisle changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Jim Wilson changed:
What|Removed |Added
CC||wilson at gcc dot gnu.org
--- Comment #7 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Thomas Koenig changed:
What|Removed |Added
Status|RESOLVED|NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #5 from Andrew Benson ---
I couldn't find anything in the OpenMP specifications which addresses this
issue - so presumably it's undefined behavior as far as OpenMP is concerned.
But it seems that internal file writes were intended to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #3 from Jakub Jelinek ---
I thought they are supposed to be, at least that is what we had unit_lock,
u->lock etc. for. So has something in libgfortran changed so that it doesn't
properly lock the units anymore?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
--- Comment #2 from Andrew Benson ---
OK - thanks. I hadn't realized that the internal I/O operations weren't
threadsafe - I guess I've just been fortunate to avoid this with previous
versions of gfortran. I'll update my code to use critical sect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78387
Thomas Koenig changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
17 matches
Mail list logo
