public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/7561: Prefetch merging code in gcc-3.1/gcc/loop.c incorect
Date: Fri, 06 Dec 2002 12:06:00 -0000 [thread overview]
Message-ID: <20021206200602.31625.qmail@sources.redhat.com> (raw)
The following reply was made to PR middle-end/7561; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Janis Johnson <janis187@us.ibm.com>
Cc: gcc-bugs@gcc.gnu.org, <redmond@ecf.utoronto.ca>, <gcc-gnats@gcc.gnu.org>
Subject: Re: middle-end/7561: Prefetch merging code in gcc-3.1/gcc/loop.c
incorect
Date: Fri, 6 Dec 2002 13:56:18 -0600 (CST)
> It was put on hold while IBM figured out new priorities for me. I plan
> to get back to it soon, this time testing performance changes on
> powerpc64-linux as well as ia64-linux. I'll separate out fixes from the
> other changes in case they can go in as bug fixes for 3.3.x and perhaps
> 3.2.x.
OK, thanks for your feedback. I put the PR back into "analyzed" mode.
It would be great if you could extract correctness patches from your
changes and apply them. (I guess, prefetching can probably never be
"wrong", it can only be useless, but you know what I mean.)
Thanks
Wolfgang
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-06 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 12:06 Wolfgang Bangerth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 11:54 bangerth
2002-12-06 11:26 Janis Johnson
2002-12-04 8:07 bangerth
2002-08-14 10:52 Janis Johnson
2002-08-09 12:05 redmond
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=20021206200602.31625.qmail@sources.redhat.com \
--to=bangerth@ticam.utexas.edu \
--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).