public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Corey Kasten <corey@materialintelligencellc.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Better performance on older version of GCC
Date: Fri, 27 Aug 2010 15:03:00 -0000	[thread overview]
Message-ID: <1282921326.2931.17.camel@MILLC-COREY> (raw)
In-Reply-To: <20100827135005.GO16898@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

On Fri, 2010-08-27 at 06:50 -0700, Nathan Froyd wrote:
> On Fri, Aug 27, 2010 at 09:44:25AM -0400, Corey Kasten wrote:
> > I find that the executable compiled on system A runs faster (on both
> > systems) than the executable compiled on system B (on both system), by a
> > factor about approximately 4 times. I have attempted to play with the
> > GCC optimizer flags and have not been able to get System B (with the
> > later GCC version) to compile code with any better performance. Could
> > someone please help figure this out?
> 
> It's almost impossible to tell what's going on without an actual
> testcase.  You might not be able to provide the actual code, but you
> could try distilling it down to something you could release.
> 
> -Nathan

Thanks for the reply Nathan.

I have attached an archive with the test case code. The code is built by
build.sh and outputs the number of microseconds to complete the
processing.

Compiling with GCC version "4.1.2 20070925 (Red Hat 4.1.2-33)" produces
code that runs in about 66% of the time than does GCC version "4.3.0
20080428 (Red Hat 4.3.0-8)"

Thanks

Corey

[-- Attachment #2: testbenchmark.100827.1050.tgz --]
[-- Type: application/x-compressed-tar, Size: 5022 bytes --]

  reply	other threads:[~2010-08-27 15:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 13:50 Corey Kasten
2010-08-27 14:20 ` H.J. Lu
2010-08-27 14:23 ` Nathan Froyd
2010-08-27 15:03   ` Corey Kasten [this message]
2010-08-27 15:40     ` Richard Guenther
2010-08-27 16:29       ` Corey Kasten
2010-08-28  1:06         ` Xinliang David Li
2010-08-28  8:23           ` Andrew Pinski
2010-08-28 10:08             ` Xinliang David Li

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=1282921326.2931.17.camel@MILLC-COREY \
    --to=corey@materialintelligencellc.com \
    --cc=froydnj@codesourcery.com \
    --cc=gcc@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).