public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: sje@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/6856: -O2 options causes Internal compiler error on hpux11.00
Date: Wed, 19 Feb 2003 16:36:00 -0000 [thread overview]
Message-ID: <20030219163600.25565.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/6856; it has been noted by GNATS.
From: Steve Ellcey <sje@cup.hp.com>
To: ebotcazou@gcc.gnu.org, corrado.giacomini@trema.com,
gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, harri.pasanen@trema.com,
nobody@gcc.gnu.org, sje@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: optimization/6856: -O2 options causes Internal compiler error on hpux11.00
Date: Wed, 19 Feb 2003 08:27:44 -0800 (PST)
No it wasn't. No one ever approved it (nor was it explicitly disapproved),
there were no comments on it at all.
Steve Ellcey
sje@cup.hp.com
> Synopsis: -O2 options causes Internal compiler error on hpux11.00
>
> Responsible-Changed-From-To: unassigned->sje
> Responsible-Changed-By: ebotcazou
> Responsible-Changed-When: Wed Feb 19 10:13:41 2003
> Responsible-Changed-Why:
> Submitter of the patch.
> State-Changed-From-To: open->feedback
> State-Changed-By: ebotcazou
> State-Changed-When: Wed Feb 19 10:13:41 2003
> State-Changed-Why:
> Steve, was your patch checked in?
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6856
next reply other threads:[~2003-02-19 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 16:36 Steve Ellcey [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 10:13 giovannibajo
2003-05-07 8:36 Dara Hazeghi
2003-02-19 17:46 Corrado Giacomini
2003-02-19 16:56 Steve Ellcey
2003-02-19 16:46 Eric Botcazou
2003-02-19 10:13 ebotcazou
2002-07-29 9:16 Steve Ellcey
2002-05-29 5:16 corrado.giacomini
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=20030219163600.25565.qmail@sources.redhat.com \
--to=sje@cup.hp.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=sje@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).