public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Laurynas Biveinis <lauras@softhome.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3374: Bootstrap failure with -O -fomit-frame-pointer
Date: Wed, 27 Nov 2002 05:52:00 -0000 [thread overview]
Message-ID: <20021119213603.31954.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/3374; it has been noted by GNATS.
From: Laurynas Biveinis <lauras@softhome.net>
To: bangerth@dealii.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/3374: Bootstrap failure with -O -fomit-frame-pointer
Date: Tue, 19 Nov 2002 23:34:28 +0200
> Synopsis: Bootstrap failure with -O -fomit-frame-pointer
> This is a rather old bootstrap failure. Can you please
> check whether this still happens with newer versions of gcc
> and report your findings?
Hello,
Unfortunatelly I do not have resources right now to check it :(
However, the failure was encountered on very common platform
i686-pc-linux-gnu, so it would be nice if someone could spare some
CPU time to do bootstrap with
BOOT_CFLAGS="-O -fomit-frame-pointer -fno-defer-pop -fno-thread-jumps"
(Those -fno-... options are not required to reproduce debugging, IIRC.
They were added just to narrow the set of active optimizations, I
think) I'll check myself as soon as I am able to. (In a month or
two...)
Laurynas
next reply other threads:[~2002-11-19 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 5:52 Laurynas Biveinis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 8:14 bangerth
2002-11-26 14:06 bangerth
2001-06-22 9:16 Laurynas Biveinis
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=20021119213603.31954.qmail@sources.redhat.com \
--to=lauras@softhome.net \
--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).