public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10171: [3.2/3.3/3.4 regression] wrong code for inlined function
Date: Sat, 22 Mar 2003 23:06:00 -0000 [thread overview]
Message-ID: <20030322230600.30072.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/10171; it has been noted by GNATS.
From: Janis Johnson <janis187@us.ibm.com>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: gcc-gnats@gcc.gnu.org, mchen@vmware.com, gcc-bugs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org, agesen@vmware.com,
mendel@vmware.com, janis187@us.ibm.com
Subject: Re: optimization/10171: [3.2/3.3/3.4 regression] wrong code for inlined function
Date: Sat, 22 Mar 2003 15:01:50 -0800
On Sat, Mar 22, 2003 at 11:22:32PM +0100, Steven Bosscher wrote:
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10171
>
> Janis,
>
> If the patch you identified really breaks stuff, then this PR should be
> in the
> category "target", agree?
Not necessarily; see Jason's comment about how -O2 does some unrolling.
The identified patch might have merely made that change (as far as this
problem is concerned).
next reply other threads:[~2003-03-22 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 23:06 Janis Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 21:06 jason
2003-03-22 22:26 Steven Bosscher
2003-03-22 21:46 Janis Johnson
2003-03-21 23:56 Jason Merrill
2003-03-21 23:36 Steven Bosscher
2003-03-21 6:17 jason
2003-03-21 6:10 jason
2003-03-20 19:09 bangerth
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=20030322230600.30072.qmail@sources.redhat.com \
--to=janis187@us.ibm.com \
--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).