public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/27692] FAIL: g++.old-deja/g++.other/init5.C execution test
Date: Tue, 11 Oct 2011 13:08:00 -0000	[thread overview]
Message-ID: <bug-27692-4-sBRzUpQqHI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-27692-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> 2011-10-11 13:08:19 UTC ---
Namespace-scope objects aren't the problem; we've always handled them fine. 
The problem is with function-local statics, which aren't constructed until the
function is called, so we can't determine the order of construction at compile
time.  We need to use atexit for them, and so for proper interleaving of
destructors we need to use atexit for namespace-scope objects as well, but that
can cause trouble with dlclose, which is why we created __cxa_atexit.


  parent reply	other threads:[~2011-10-11 13:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-27692-4@http.gcc.gnu.org/bugzilla/>
2011-10-09 16:00 ` paolo.carlini at oracle dot com
2011-10-10 21:19 ` dave.anglin at bell dot net
2011-10-10 21:45 ` paolo.carlini at oracle dot com
2011-10-11  1:10 ` jason at gcc dot gnu.org
2011-10-11  1:27 ` paolo.carlini at oracle dot com
2011-10-11 12:07 ` dave.anglin at bell dot net
2011-10-11 13:08 ` jason at gcc dot gnu.org [this message]
2011-10-11 14:20 ` dave.anglin at bell dot net
2011-10-11 14:39 ` jason at gcc dot gnu.org
2006-05-20 20:36 [Bug c++/27692] New: " danglin at gcc dot gnu dot org
2006-05-21  5:34 ` [Bug c++/27692] " pinskia at gcc dot gnu dot org
2006-06-05 16:51 ` sje at cup dot hp dot com
2006-06-05 17:07 ` pinskia at gcc dot gnu dot org
2006-06-05 17:10 ` pinskia at gcc dot gnu dot 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-27692-4-sBRzUpQqHI@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).