public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Revital Eres <ERES@il.ibm.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Ayal Zaks <ZAKS@il.ibm.com>,
	Mircea Namolaru <NAMOLARU@il.ibm.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [Patch] Splitting memory references during unrolling (resubmission)
Date: Thu, 18 Nov 2004 14:23:00 -0000	[thread overview]
Message-ID: <OF2DE73FB1.6E1C564E-ONC2256F4F.005BC401-C2256F50.0047E919@il.ibm.com> (raw)
In-Reply-To: <200410150347.i9F3lfV10588@makai.watson.ibm.com>

David Edelsohn <dje@watson.ibm.com> wrote on 15/10/2004 05:47:41:

>    What is the current SPEC performance benefit from this patch?
> 
> Thanks, David


Hello,

This patch gains ~1% improvements on overall CINTPEC2000 on 
powerpc-linux when the number of times this optimization 
is applied in each loop is restricted to one
(I can add this restriction if this patch will be accepted); 
where gap gains ~5% improvements and bzip2 ~1%.
In CFPPEC2000 there was no significant improvements 
except swim which gained 3% improvement but mesa,
facerec and wupwise show a regression of about 1%
each.

Revital


  reply	other threads:[~2004-11-18 13:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 13:14 Revital Eres
2004-10-15  3:48 ` David Edelsohn
2004-11-18 14:23   ` Revital Eres [this message]
2004-11-18 15:46     ` David Edelsohn
  -- strict thread matches above, loose matches on Subject: below --
2004-08-18 16:39 Revital Eres
2004-08-09  7:03 Revital Eres
2004-08-09  7:15 ` Steven Bosscher
2004-08-09  7:19   ` Steven Bosscher
2004-08-21 16:41 ` Zdenek Dvorak
2004-09-02  7:08   ` Revital Eres

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=OF2DE73FB1.6E1C564E-ONC2256F4F.005BC401-C2256F50.0047E919@il.ibm.com \
    --to=eres@il.ibm.com \
    --cc=NAMOLARU@il.ibm.com \
    --cc=ZAKS@il.ibm.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc-patches@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).