public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org
To: ebotcazou@gcc.gnu.org, ehrhardt@mathematik.uni-ulm.de,
	gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	papadopo@shfj.REMOVE.cea.DECOY.fr
Subject: Re: optimization/8396: [3.2/3.3/3.4 regression] [sparc] optimizer ICE
Date: Tue, 11 Mar 2003 13:54:00 -0000	[thread overview]
Message-ID: <20030311135424.10185.qmail@sources.redhat.com> (raw)

Synopsis: [3.2/3.3/3.4 regression] [sparc] optimizer ICE

Responsible-Changed-From-To: unassigned->ebotcazou
Responsible-Changed-By: ebotcazou
Responsible-Changed-When: Tue Mar 11 13:54:23 2003
Responsible-Changed-Why:
    Investigating.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8396


             reply	other threads:[~2003-03-11 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 13:54 ebotcazou [this message]
2003-03-14 15:07 ebotcazou

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=20030311135424.10185.qmail@sources.redhat.com \
    --to=ebotcazou@gcc.gnu.org \
    --cc=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=papadopo@shfj.REMOVE.cea.DECOY.fr \
    /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).