public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dhazeghi at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/9249] bootstrap fails with --enable-__cxa-atexit on Solaris
Date: Thu, 11 Dec 2003 09:12:00 -0000 [thread overview]
Message-ID: <20031211091203.2813.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030109082607.9249.cludwig@cdc.informatik.tu-darmstadt.de>
------- Additional Comments From dhazeghi at yahoo dot com 2003-12-11 09:11 -------
How's this look (I lifted most of it directly from configure.in)?
--- doc/install.texi.old Thu Dec 11 00:56:57 2003
+++ doc/install.texi Thu Dec 11 01:08:53 2003
@@ -938,6 +938,14 @@
AltiVec code when appropriate. This option is only available for
PowerPC systems.
+@item --enable-__cxa_atexit
+Define if you want to use __cxa_atexit, rather than atexit, to
+register C++ destructors for local statics and global objects.
+This is essential for fully standards-compliant handling of
+destructors, but requires __cxa_atexit in libc. This option is currently
+only available on sytems with GNU libc. When enabled, this will cause
+@option{-fuse-cxa-exit} to be passed by default.
+
@item --enable-target-optspace
Specify that target
libraries should be optimized for code space instead of code speed.
Regarding a configure check for this, I haven't got any good ideas. I gues we could blacklist
systems whose triplet didn't end in GNU, but that seems unclean. Ideas?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9249
next prev parent reply other threads:[~2003-12-11 9:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030109082607.9249.cludwig@cdc.informatik.tu-darmstadt.de>
2003-10-24 23:10 ` dhazeghi at yahoo dot com
2003-10-25 0:09 ` pme at gcc dot gnu dot org
2003-12-01 8:57 ` ebotcazou at gcc dot gnu dot org
2003-12-02 17:15 ` dhazeghi at yahoo dot com
2003-12-02 18:29 ` ebotcazou at gcc dot gnu dot org
2003-12-11 9:12 ` dhazeghi at yahoo dot com [this message]
2003-12-11 10:05 ` cludwig at cdc dot informatik dot tu-darmstadt dot de
2003-12-11 18:29 ` ebotcazou at gcc dot gnu dot org
2003-12-11 20:42 ` dhazeghi at yahoo dot com
2003-12-20 8:46 ` pinskia at gcc dot gnu dot org
2004-01-10 1:36 ` neroden at gcc dot gnu dot org
2004-01-10 22:40 ` steven at gcc dot gnu dot org
2004-01-10 22:42 ` steven at gcc dot gnu dot org
2004-01-11 6:47 ` ebotcazou at gcc dot gnu dot org
2004-01-14 3:49 ` pinskia at gcc dot gnu dot org
2004-01-14 5:29 ` ebotcazou at gcc dot gnu dot org
2004-01-16 4:06 ` dhazeghi at yahoo dot com
2004-01-17 8:01 ` dhazeghi at yahoo dot com
2004-01-31 4:12 ` cvs-commit at gcc dot gnu dot org
2004-01-31 4:15 ` cvs-commit at gcc dot gnu dot org
2004-01-31 4:18 ` cvs-commit at gcc dot gnu dot org
2004-01-31 4:19 ` 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=20031211091203.2813.qmail@sources.redhat.com \
--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).