This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
to use_cxa_atexit or not to use_cxa_atexit
- From: Jack Howarth <howarth at bromo dot msbb dot uc dot edu>
- To: gcc at gcc dot gnu dot org
- Date: Sat, 1 Jun 2002 18:01:05 -0400 (EDT)
- Subject: to use_cxa_atexit or not to use_cxa_atexit
Hi,
I am still confused on the consensus here as to the rationality of
a distro setting the flag_use_cxa_atexit to a non-zero value. From
comments on gcc-patches I got the impression that for Linux there
is absolutely no merit to using __cxa_atexit instead of atexit.
Is that also the case with hurd and bsd? I ask because debian sid is
still using their g++-cxa-atexit.dpatch in their new gcc 3.1.1-pre1
based packages. If all the other distros build binaries with gcc 3.1.1
without use_cxa_atexit being enabled, won't that create problems for
debian in terms of exchanging binaries with other distros? Also with
HJ Lu backing out his configure changes from the trunk I got the
impression that an effort was going to be made to purge out the
__cxa_atexit stuff from gcc. Or is that incorrect? Thanks in advance
for any clarifications.
Jack
ps Currently binutils can not pass all of its make check with
use_cxa_atexit enabled so definitely some debugging is left to
be done on that feature.