From: Richard Biener <rguenther@suse.de>
To: Pat Haugen <pthaugen@linux.vnet.ibm.com>
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
hjl.tools@gmail.com
Subject: Re: [PATCH][RFC] Add -fno-aggressive-loop-optimizations
Date: Thu, 31 Jan 2013 09:06:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1301310954300.6889@zhemvz.fhfr.qr> (raw)
In-Reply-To: <5109579A.7070004@linux.vnet.ibm.com>
On Wed, 30 Jan 2013, Pat Haugen wrote:
> On 01/29/2013 04:53 AM, Richard Biener wrote:
> > I'm curious about the affect of -fno-aggressive-loop-optimizations
> > on SPEC CPU 2006 numbers (not curious enough to try for myself
> > though). Both on extra PASSes for official latest sources
> > (I have no access to those) and on performance.
> The patch/option result in both 464.h264ref and 416.gamess passing (as opposed
> to infinite loop). As for performance, I didn't see any difference outside of
> noise range for both 32-bit and 64-bit runs on PowerPC.
Ok, I'll go ahead and apply the patch then.
Richard.
next prev parent reply other threads:[~2013-01-31 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 10:53 Richard Biener
2013-01-30 17:26 ` Pat Haugen
2013-01-31 9:06 ` Richard Biener [this message]
2013-01-31 9:11 ` Richard Biener
2013-02-16 23:43 ` Gerald Pfeifer
2013-02-18 9:10 ` Richard Biener
2013-01-30 16:48 Dominique Dhumieres
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=alpine.LNX.2.00.1301310954300.6889@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=pthaugen@linux.vnet.ibm.com \
/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).