This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/33704] AIX runs c++ constructors in incorrect order
- From: "ajd at gentrack dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Oct 2007 01:44:22 -0000
- Subject: [Bug target/33704] AIX runs c++ constructors in incorrect order
- References: <bug-33704-8038@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #21 from ajd at gentrack dot com 2007-10-19 01:44 -------
Created an attachment (id=14372)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14372&action=view)
support -blazy, add option to disable
I suggest exportinitfini_flag is enabled by default or atleast for the build of
libstdc++.a and libgcc_s.a.
It should have minimal impact/risk.
initdependents_flag has risk/impact attached. You may want to reverse the
default.
My case for having it on by default:
To use exceptions within global constructors a module needs to be linked with
initdependents_flag enabled.
I believe there are other functions in libstdc++ that depend on initialization
order. I do not have specifics.
Assuming AIX was the only OS that works this way, it allows removal of these
types of workarounds:
http://gcc.gnu.org/ml/libstdc++/2001-01/msg00369.html
--
ajd at gentrack dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #14327|0 |1
is obsolete| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33704