public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/17835] [4.0 Regression] stage2 compiler is broken because it is built with -fomit-frame-pointer
Date: Tue, 05 Oct 2004 11:26:00 -0000	[thread overview]
Message-ID: <20041005112621.23115.qmail@sourceware.org> (raw)
In-Reply-To: <20041005072827.17835.rschiele@uni-mannheim.de>



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|bootstrap                   |target
           Keywords|                            |build, ice-on-valid-code,
                   |                            |wrong-code
            Summary|stage2 compiler is broken   |[4.0 Regression] stage2
                   |because it is built with -  |compiler is broken because
                   |fomit-frame-pointer         |it is built with -fomit-
                   |                            |frame-pointer
   Target Milestone|---                         |4.0.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17835


  parent reply	other threads:[~2004-10-05 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05  7:28 [Bug bootstrap/17835] New: " rschiele at uni-mannheim dot de
2004-10-05  9:14 ` [Bug bootstrap/17835] " ebotcazou at gcc dot gnu dot org
2004-10-05 11:26 ` pinskia at gcc dot gnu dot org [this message]
2004-10-06 15:37 ` [Bug target/17835] [4.0 Regression] " ebotcazou at gcc dot gnu dot org
2004-10-06 22:29 ` [Bug middle-end/17835] " ebotcazou at gcc dot gnu dot org
2004-10-06 22:55 ` pinskia at gcc dot gnu dot org
2004-10-07  5:56 ` cvs-commit at gcc dot gnu dot org
2004-10-07  5:59 ` ebotcazou 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=20041005112621.23115.qmail@sourceware.org \
    --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).