public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2907: libstdc++ compiled with optimization fails to initialize ios.
Date: Tue, 22 May 2001 20:16:00 -0000 [thread overview]
Message-ID: <20010523031602.18779.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR libstdc++/2907; it has been noted by GNATS.
From: Carlo Wood <carlo@alinoe.com>
To: gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: libstdc++/2907: libstdc++ compiled with optimization fails to initialize ios.
Date: Wed, 23 May 2001 05:11:04 +0200
I hate it when I make errors :/ (but at least I correct myself within 10 minutes usually ;).
On Wed, May 23, 2001 at 04:58:57AM +0200, Carlo Wood wrote:
> -fdefer-pop -fomit-frame-pointer : core
> -fthread-jumps -fomit-frame-pointer : no core
>
>
> Final conclusion: The problem shows itself when compiling locale.cc with
> "-fdefer-pop -fomit-frame-pointer", or to be exact:
>
> /usr/src/gcc/gcc-objdir-3.0/i686-pc-linux-gnu/libstdc++-v3/src>make
> /bin/sh ../libtool --tag CXX --mode=compile /usr/src/gcc/gcc-objdir-3.0/gcc/xgcc \
> -B/usr/src/gcc/gcc-objdir-3.0/gcc/ -nostdinc++ -L/usr/src/gcc/gcc-objdir-3.0/i686-pc-linux-gnu/libstdc++-v3/src \
> -L/usr/src/gcc/gcc-objdir-3.0/i686-pc-linux-gnu/libstdc++-v3/src/.libs -B/usr/local/gcc-3.0/i686-pc-linux-gnu/bin/ \
> -B/usr/local/gcc-3.0/i686-pc-linux-gnu/lib/ -isystem /usr/local/gcc-3.0/i686-pc-linux-gnu/include -nostdinc++ \
> -I/usr/src/gcc/gcc-cvs-3.0/libstdc++-v3/include -I/usr/src/gcc/gcc-cvs-3.0/libstdc++-v3/include/std \
> -I/usr/src/gcc/gcc-cvs-3.0/libstdc++-v3/include/c_std -I../include \
> -I/usr/src/gcc/gcc-cvs-3.0/libstdc++-v3/libsupc++ -I../libio -I/usr/src/gcc/gcc-cvs-3.0/libstdc++-v3/libio \
> -I/usr/src/gcc/gcc-cvs-3.0/libstdc++-v3/libmath \
> -fthread-jumps -fomit-frame-pointer -D_GNU_SOURCE \
^^^^^^^^^^^^^^
> -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once \
> -ffunction-sections -fdata-sections -g -c /usr/src/gcc/gcc-cvs-3.0/libstdc++-v3/src/locale.cc
That "-fthread-jumps" must be "-fdefer-pop" thus.
Sigh, ... (perhaps it the 5:09 am ... bed time?)
--
Carlo Wood <carlo@alinoe.com>
next reply other threads:[~2001-05-22 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 20:16 Carlo Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-22 20:06 Carlo Wood
2001-05-22 18:26 Phil Edwards
2001-05-22 17:16 carlo
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=20010523031602.18779.qmail@sourceware.cygnus.com \
--to=carlo@alinoe.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).