This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: static constructors/destructors and atexit
- To: Joe Buck <jbuck at synopsys dot com>
- Subject: Re: static constructors/destructors and atexit
- From: Kamil Iskra <kamil at dwd dot interkom dot pl>
- Date: Thu, 13 Aug 1998 22:02:02 +0200 (EEST)
- cc: Steven Parkes <parkes at sierravista dot com>, tv at pobox dot com, oliva at dcc dot unicamp dot br, egcs at cygnus dot com
On Tue, 11 Aug 1998, Joe Buck wrote:
> > As someone mentioned, this is not standards-conforming. The standard
> > requires that local static destruction be interleaved with atexit()
> > callbacks and this won't do that.
> We can conform to the standard simply by using atexit() to do local
> static destruction.
[snip]
Excuse me, but why complicate it so much? Why can't we simply make the
compiler replace the user-level atexit() calls with our own atexit() with
no limits? This way we would conform to the standard, right?
/ Kamil Iskra AmigaOS Linux/i386 Linux/m68k \
| GeekGadgets GCC maintainer UNIX system administrator |
| iskra@student.uci.agh.edu.pl kiskra@ernie.icslab.agh.edu.pl |
\ kamil@dwd.interkom.pl http://student.uci.agh.edu.pl/~iskra /