public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/11189] Destructors for static local objects use limited atexit().
       [not found] <20030613180351.11189.bill.wade@advantica.biz>
@ 2003-07-05 15:11 ` pinskia at physics dot uc dot edu
  2003-08-03 18:44 ` neroden at gcc dot gnu dot org
  2003-08-18  1:48 ` mmitchel at gcc dot gnu dot org
  2 siblings, 0 replies; 3+ messages in thread
From: pinskia at physics dot uc dot edu @ 2003-07-05 15:11 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


pinskia at physics dot uc dot edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2003-07-05 15:11:29
               date|                            |


------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-05 15:11 -------
I can reproduce it on powerpc-apple-darwin6.6 but I had to up to 60 as darwin has a limit 
of 50.  I think on a platform with __cxa_atexit, I think this is fixed but not all platforms 
support it.


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

* [Bug c++/11189] Destructors for static local objects use limited atexit().
       [not found] <20030613180351.11189.bill.wade@advantica.biz>
  2003-07-05 15:11 ` [Bug c++/11189] Destructors for static local objects use limited atexit() pinskia at physics dot uc dot edu
@ 2003-08-03 18:44 ` neroden at gcc dot gnu dot org
  2003-08-18  1:48 ` mmitchel at gcc dot gnu dot org
  2 siblings, 0 replies; 3+ messages in thread
From: neroden at gcc dot gnu dot org @ 2003-08-03 18:44 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From neroden at gcc dot gnu dot org  2003-08-03 18:44 -------
I'm not sure we should even try to fix this on platforms without __cxa_atexit,
given the many other faults related to that absence.  :-/


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

* [Bug c++/11189] Destructors for static local objects use limited atexit().
       [not found] <20030613180351.11189.bill.wade@advantica.biz>
  2003-07-05 15:11 ` [Bug c++/11189] Destructors for static local objects use limited atexit() pinskia at physics dot uc dot edu
  2003-08-03 18:44 ` neroden at gcc dot gnu dot org
@ 2003-08-18  1:48 ` mmitchel at gcc dot gnu dot org
  2 siblings, 0 replies; 3+ messages in thread
From: mmitchel at gcc dot gnu dot org @ 2003-08-18  1:48 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


mmitchel at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


------- Additional Comments From mmitchel at gcc dot gnu dot org  2003-08-18 01:48 -------
There is no portable way to replace atexit.

Furthermore, it is incorrect not to use atexit; the order of destruction of
function local statics must be interleaved with atexit calls.


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

end of thread, other threads:[~2003-08-18  1:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20030613180351.11189.bill.wade@advantica.biz>
2003-07-05 15:11 ` [Bug c++/11189] Destructors for static local objects use limited atexit() pinskia at physics dot uc dot edu
2003-08-03 18:44 ` neroden at gcc dot gnu dot org
2003-08-18  1:48 ` mmitchel 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).