public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jgrimm2 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/17950] Over Aggressive Use of Data Cache Touch Instructions During FDO Date: Thu, 18 Nov 2004 01:32:00 -0000 [thread overview] Message-ID: <20041118013227.26606.qmail@sourceware.org> (raw) In-Reply-To: <20041012174801.17950.steinmtz@us.ibm.com> ------- Additional Comments From jgrimm2 at us dot ibm dot com 2004-11-18 01:32 ------- Hmmm... looks like a couple things (maybe more) come in to play here. First, value-profile code doesn't seem to merge prefetches (among other things). That is, it should be pretty easy (crude?) to track the last prefetch and not prefetch addresses that look close. Doing so seems to help this test case quite a bit (96 prefetches down to 24), but probably not enough..... as it seems that the loop unroller comes through afterwards and does its damage too. Might need to teach the unroller about prefetch a bit too?? -- What |Removed |Added ---------------------------------------------------------------------------- CC| |jgrimm2 at us dot ibm dot | |com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17950
next prev parent reply other threads:[~2004-11-18 1:32 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-12 17:48 [Bug target/17950] New: " steinmtz at us dot ibm dot com 2004-10-12 17:51 ` [Bug rtl-optimization/17950] " pinskia at gcc dot gnu dot org 2004-10-12 19:45 ` pinskia at gcc dot gnu dot org 2004-11-17 14:34 ` nathan at gcc dot gnu dot org 2004-11-17 14:41 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2004-11-18 1:32 ` jgrimm2 at us dot ibm dot com [this message] 2004-11-23 1:43 ` jgrimm2 at us dot ibm dot com 2005-07-29 11:46 ` pinskia at gcc dot gnu dot org
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=20041118013227.26606.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).