public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8835: mcore-elf bootstrap ICE at expr.c:2771
Date: Sat, 01 Feb 2003 14:26:00 -0000	[thread overview]
Message-ID: <20030201142601.20797.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/8835; it has been noted by GNATS.

From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: joel@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/8835: mcore-elf bootstrap ICE at expr.c:2771
Date: Sat, 1 Feb 2003 15:25:16 +0100

 On Fri, Jan 31, 2003 at 06:25:56PM -0000, joel@gcc.gnu.org wrote:
 > Synopsis: mcore-elf bootstrap ICE at expr.c:2771
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: joel
 > State-Changed-When: Fri Jan 31 18:25:56 2003
 > State-Changed-Why:
 >     Still occurs on gcc 3.2.2 20030130 (prerelease)
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8835
 
 Why do you change the state to feedback? What kind of feedback do you
 expect and you is supposed to give feedback? Also it would be helpful
 if you could attach preprocessed source that reproduces the problem.
 This will enable us to move the report from bootstrap to ICE on legal
 which is a great help for people trying to reproduce and fix this.
 
     regards   Christian
 
 -- 
 THAT'S ALL FOLKS!


             reply	other threads:[~2003-02-01 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-01 14:26 Christian Ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 18:10 Joel Sherrill
2003-05-12 11:46 giovannibajo
2003-01-31 18:25 joel
2002-12-05 15:16 joel

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=20030201142601.20797.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --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).