This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] Re: Wrong destruction order of static objects in g++
- To: Klaus-Georg Adams <Klaus-Georg dot Adams at chemie dot uni-karlsruhe dot de>
- Subject: [patch] Re: Wrong destruction order of static objects in g++
- From: Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Date: 04 Jun 1998 16:25:56 -0300
- Cc: egcs-bugs at cygnus dot com, jkanze at otelo dot ibmmail dot com
- Cc: egcs-patches at cygnus dot com
- References: <199806041257.OAA19808@achibm5.chemie.uni-karlsruhe.de>
Klaus-Georg Adams <Klaus-Georg.Adams@chemie.uni-karlsruhe.de> writes:
> James Kanze (jkanze@otelo.ibmmail.com) has given me a nice test case
> which shows that egcs (and gcc-2.7.2) get the destruction order of
> static objects wrong.
> Is there a way in the old-deja framework to compare the output of a
> program to a default?
I don't think so, but it's easy to work around this problem. Here's a
patch that adds this test case.
BTW, it is ok to Bcc to egcs-patches? I didn't this time, in fear
that someone that handles patches uses a tool such as Gnus or procmail
for classifying mail; if I had Bcc'ed to egcs-patches, they would
probably be unable to notice that.
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
init5.diff