public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54601] AIX uses atexit which causes unloading of shared modules to break
Date: Wed, 30 Jan 2013 16:59:00 -0000	[thread overview]
Message-ID: <bug-54601-4-2odnC1DOaS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54601-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54601

--- Comment #7 from David Edelsohn <dje at gcc dot gnu.org> 2013-01-30 16:59:13 UTC ---
Created attachment 29307
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29307
cxa_atexit implementation in libgcc

This version of the patch implements __cxa_atexit and __cxa_finalize in libgcc,
not libsupc++, with no modifications to collect2.  I am not sure if using a low
priority C destructor to run __cxa_finalize early in the destructor list is
correct. The original collect2 patch ran it last, after other destructors,
which I believe is incorrect and does not match crtstuff.c semantics for ELF. 
When I configured GCC with the patch and --enable__cxa-atexit, I saw a few
additional C++ errors in the testsuite.


  parent reply	other threads:[~2013-01-30 16:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-16 14:36 [Bug c++/54601] New: " pedzsan at gmail dot com
2012-09-16 14:39 ` [Bug c++/54601] " pedzsan at gmail dot com
2012-09-16 14:40 ` pedzsan at gmail dot com
2012-09-16 18:47 ` redi at gcc dot gnu.org
2012-09-17 14:18 ` pedzsan at gmail dot com
2012-10-01 16:31 ` paolo.carlini at oracle dot com
2012-10-03 17:53 ` dje at gcc dot gnu.org
2013-01-30 16:59 ` dje at gcc dot gnu.org [this message]
2013-01-30 21:58 ` dje at gcc dot gnu.org
2013-01-31  4:53 ` dje at gcc dot gnu.org
2013-01-31  5:50 ` pedzsan at gmail dot com
2013-01-31  6:11 ` dje at gcc dot gnu.org
2013-02-01 20:27 ` dje at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-54601-4-2odnC1DOaS@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).