From: Denis Zaitsev <zzz@anda.ru>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org, linux-gcc@vger.kernel.org
Subject: Re: [BUG] GCC 3.4.3/x86: -fomit-frame-pointer cause a lot of test failures for libstdc++
Date: Tue, 28 Dec 2004 02:14:30 +0500 [thread overview]
Message-ID: <20041228021429.B1437@natasha.ward.six> (raw)
In-Reply-To: <D23532B5-53CE-11D9-95A4-000A95D692F4@physics.uc.edu>; from pinskia@physics.uc.edu on Tue, Dec 21, 2004 at 11:06:13PM -0500
On Tue, Dec 21, 2004 at 11:06:13PM -0500, Andrew Pinski wrote:
>
> On Dec 21, 2004, at 10:42 PM, Denis Zaitsev wrote:
>
> > I've built GCC with -fomit-frame-pointer and -fno-omit-frame-pointer.
> > I mean either of these flags is present in both the exported shell
> > variables CFLAGS and CXXFLAGS and also in the BOOT_CFLAGS variable
> > from gcc/Makefile. Both the builds was successfull. And these are
> > some results of 'make check':
>
> I would not doubt this is the -fomit-frame-pointer exception handling
> bug which was fixed in 3.4.4, 3.3.6, and 4.0.0.
> See PR 17220 and 6764.
And these are the results for GCC 3.4-20041224:
=== libstdc++ Summary ===
# of expected passes 2373
# of unexpected failures 357
# of expected failures 7
So, there are still the same bugs.
next prev parent reply other threads:[~2004-12-27 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 3:42 [BUG] GCC 3.4.3/x86: -fomit-frame-pointer cause a lot of test failures for libstdc++ Denis Zaitsev
2004-12-22 4:06 ` Andrew Pinski
2004-12-22 4:34 ` Denis Zaitsev
2004-12-22 4:38 ` Andrew Pinski
2004-12-22 20:13 ` Denis Zaitsev
2004-12-22 22:20 ` Denis Zaitsev
2004-12-27 21:14 ` Denis Zaitsev [this message]
2004-12-28 4:08 ` Denis Zaitsev
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=20041228021429.B1437@natasha.ward.six \
--to=zzz@anda.ru \
--cc=gcc@gcc.gnu.org \
--cc=linux-gcc@vger.kernel.org \
--cc=pinskia@physics.uc.edu \
/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 NNTP newsgroup(s).