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: Wed, 14 Aug 2002 10:52:00 -0000 [thread overview] Message-ID: <20020814165601.22563.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: redmond@ecf.utoronto.ca Cc: gcc-gnats@gcc.gnu.org Subject: Re: middle-end/7561: Prefetch merging code in gcc-3.1/gcc/loop.c incorect Date: Wed, 14 Aug 2002 09:46:02 -0700 On Fri, Aug 09, 2002 at 05:58:32PM -0000, redmond@ecf.utoronto.ca wrote: > > >Number: 7561 > >Category: middle-end > >Synopsis: Prefetch merging code in gcc-3.1/gcc/loop.c incorect Wow, someone is looking at the prefetch optimization code! I'm still catching up on mailing lists after a two-week vacation and didn't see your bug report until just now. In June I posted some changes to the way the prefetches are merged, and changed things in general to handle "sparse" prefetches, for which we prefetch only the cache lines containing data that will be used rather than every cache line within the section of the array being used. I had asked Jan Hubicka to take a look at it, but that was when he was in the middle of lots of other things and I never heard anything from him. If you're interested in this optimization, please take a look at http://gcc.gnu.org/ml/gcc-patches/2002-06/msg00660.html. I can update the patch to apply to the current CVS tree, which I've been meaning to do anyway; I've been distracted by other things lately. I've also got some other tweaks locally that help some of the SPEC CPU2000 floating point tests. The new code as written can't be used because it's much slower, but it's meant to demonstrate changes to how prefetches are used; once that looks OK it can be changed to do the same work more quickly. Janis Johnson IBM Linux Technology Center
next reply other threads:[~2002-08-14 16:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-14 10:52 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-06 11:26 Janis Johnson 2002-12-04 8:07 bangerth 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=20020814165601.22563.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: linkBe 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).