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: middle-end/7561: Prefetch merging code in gcc-3.1/gcc/loop.c incorect
Date: Fri, 06 Dec 2002 11:26:00 -0000	[thread overview]
Message-ID: <20021206192602.1600.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/7561; it has been noted by GNATS.

From: Janis Johnson <janis187@us.ibm.com>
To: bangerth@dealii.org, anis187@us.ibm.com, gcc-bugs@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, redmond@ecf.utoronto.ca,
   gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: middle-end/7561: Prefetch merging code in gcc-3.1/gcc/loop.c incorect
Date: Fri, 6 Dec 2002 11:21:16 -0800

 On Wed, Dec 04, 2002 at 04:07:23PM -0000, bangerth@dealii.org wrote:
 > Synopsis: Prefetch merging code in gcc-3.1/gcc/loop.c incorect
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Wed Dec  4 08:07:23 2002
 > State-Changed-Why:
 >     Janis, you had a patch for this some time back. Can you say
 >     what the status of this is?
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7561
 
 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.
 
 Janis


             reply	other threads:[~2002-12-06 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 11:26 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-06 12:06 Wolfgang Bangerth
2002-12-06 11:54 bangerth
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=20021206192602.1600.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).