This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
No mention of 2.95.3's "atexit" problem on gcc home page
- To: gcc-help at gcc dot gnu dot org
- Subject: No mention of 2.95.3's "atexit" problem on gcc home page
- From: Chris Rankin <rankincj at yahoo dot com>
- Date: Mon, 17 Sep 2001 13:47:22 -0700 (PDT)
Hi,
I was just about to upgrade my glibc-2.2.3 to
glibc-2.2.4 when I heard dark rumours that no 2.95.x
compiler could compile glibc-2.2. I found this quite
scary because *both* my boxes have glibc-2.2.3
compiled with gcc-2.95.3+nss-patch, which presumably
means that I have an "atexit-bug" waiting to happen...
I have scoured the Internet and uncovered two patches
for gcc:
2001-03-21 Jakub Jelinek <jakub@redhat.com>
* crtstuff.c (init_dummy): Use CRT_END_INIT_DUMMY if
defined.
Remove ia32 linux PIC kludge and move it...
* config/i386/linux.h (CRT_END_INIT_DUMMY): ...here.
And then this later one for creating weak symbols:
* rtl.h (SYMBOL_REF_WEAK): New macro.
* rtlanal.h (rtx_addr_can_trap): Use it, a weak
SYMBOL_REF can trap.
* varasm.c (make_decl_rtl): Mark SYMBOL_REF weak if
necessary.
* rtl.texi (SYMBOL_REF_WEAK): Document it.
* gcc.texi: Remove wrong description.
Now I'm hoping that these are the right patches and
the right *versions* of the patches. However, they
would both seem like excellent candidates to be posted
on
http://gcc.gnu.org/install/specific.html
They're not there right now; maybe someone could add
them?
Cheers,
Chris
__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/