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/37395] [4.4 Regression] Bootstrap fails in stage 2 due to segfault compiling c-parser
Date: Tue, 09 Sep 2008 19:28:00 -0000	[thread overview]
Message-ID: <20080909192730.9405.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37395-12387@http.gcc.gnu.org/bugzilla/>



-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu dot
                   |                            |org
           Keywords|                            |wrong-code
            Summary|Bootstrap fails in stage 2  |[4.4 Regression] Bootstrap
                   |due to segfault compiling c-|fails in stage 2 due to
                   |parser                      |segfault compiling c-parser
   Target Milestone|---                         |4.4.0


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


  parent reply	other threads:[~2008-09-09 19:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 11:09 [Bug target/37395] New: " tbm at cyrius dot com
2008-09-06 11:10 ` [Bug target/37395] " tbm at cyrius dot com
2008-09-06 17:51 ` daney at gcc dot gnu dot org
2008-09-07 17:31 ` daney at gcc dot gnu dot org
2008-09-09 19:25 ` tbm at cyrius dot com
2008-09-09 19:28 ` pinskia at gcc dot gnu dot org [this message]
2008-09-09 19:29 ` [Bug target/37395] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-09-11 15:37 ` tbm at cyrius dot com
2008-09-11 21:01 ` nemet at gcc dot gnu dot org
2008-09-11 21:47 ` nemet at gcc dot gnu dot org
2008-09-11 21:49 ` pinskia at gcc dot gnu dot org
2008-09-12 14:27 ` jakub 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=20080909192730.9405.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).