public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/14943] New: [gfortran] read/write code generation is not thread safe
@ 2004-04-13 20:15 pinskia at gcc dot gnu dot org
  2004-04-15  7:01 ` [Bug fortran/14943] " pinskia at gcc dot gnu dot org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-04-13 20:15 UTC (permalink / raw)
  To: gcc-bugs

I do not know if this was intentional or not but the code generation for read/write is not 
thread safe as you are writting to a global variable.  Mybe instead defining a struct and 
passing to the functions will cause it to be thread safe.

-- 
           Summary: [gfortran] read/write code generation is not thread safe
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: minor
          Priority: P2
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14943


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-05-24  1:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-13 20:15 [Bug fortran/14943] New: [gfortran] read/write code generation is not thread safe pinskia at gcc dot gnu dot org
2004-04-15  7:01 ` [Bug fortran/14943] " pinskia at gcc dot gnu dot org
2004-04-15 12:43 ` pinskia at gcc dot gnu dot org
2004-05-24 20:49 ` pinskia at gcc dot gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).