--- Comment #19 from Jerry_V_DeLisle at rl dot gov 2008-02-07 15:54 ---
Writing to an internal unit is nothing more than a fancy (formatted)
assignment. Each thread allocates its own unit structure. Its not like file
I/O where threads are accessing a common shared resource.
I should
--- Comment #10 from Jerry_V_DeLisle at rl dot gov 2008-02-06 20:25 ---
Reply to comment #9:
This is a very important observation. I have checked the code and we have code
that free's the internal unit (free_internal_unit) and I have confirmed that it
is called correctly after
--- Comment #14 from Jerry_V_DeLisle at rl dot gov 2008-01-30 18:04 ---
The pr19925 segfault is close by the segfault here but not the same. I am
working on a patch for that one. What is becoming clear is that we are not
handling expansion of constructors very well yet.
Also, I will
--- Comment #16 from Jerry_V_DeLisle at rl dot gov 2008-01-29 15:29 ---
The segfault here is the same segfault I reported in 34828 yesterday. I have a
patch all ready for that part.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19925
