This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] to gcc: use xexit/xatexit in fixinc
- To: msokolov at ivan dot Harhan dot ORG (Michael Sokolov)
- Subject: Re: [patch] to gcc: use xexit/xatexit in fixinc
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 02 Jan 2001 00:08:59 -0200
- Cc: gcc-patches at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <0101020152.AA06166@ivan.Harhan.ORG>
On Jan 1, 2001, msokolov@ivan.Harhan.ORG (Michael Sokolov) wrote:
> Alexandre Oliva <aoliva@redhat.com> wrote:
>> The unfortunate thing is that, since there aren't that
>> many systems out there that don't offer atexit(), the fallback won't
>> be tested as much.
> Well, if 4.3BSD ever breaks, expect me to yell and scream right away. :-)
If have to be able to notice the problem first. It isn't always easy
to notice that a certain destructor action wasn't executed.
Sometimes, you'll just get a file left over, that might be deleted by
something else, so it may take a while until you notice it.
>> Makes me wonder whether we shouldn't just switch
>> to xatexit()/xexit() on *all* systems, so that we get the same exit
>> code exercised on all platforms.
> ! AC_CHECK_FUNCS(atexit strtoul bsearch putenv popen bcopy \
This tests a property of the host, but fixing is built for and runs on
the build machine. We can't use autoconf in this case, unless we
introduce additional machinery to detect properties of the build
machine.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me