From: Andrew Haley <aph@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: gcc@gcc.gnu.org, Howard Chu <hyc@highlandsun.com>
Subject: Re: [Fwd: performance with gcc -O0/-O2]
Date: Tue, 27 Nov 2007 18:13:00 -0000 [thread overview]
Message-ID: <18252.18256.964029.837816@zebedee.pink> (raw)
In-Reply-To: <p73sl2r8z6q.fsf@bingen.suse.de>
Andi Kleen writes:
> Andrew Haley <aph@redhat.com> writes:
>
> > Howard Chu writes:
> >
> > > A bit of a minor mystery. Not a problem, just a curiosity. If
> > > someone knew off the top of their head a reason for it, that'd be
> > > cool, but otherwise no sweat.
> >
> > It's possible, although unlikley, that the optimized code has worse
> > cache behaviour. No way to know better without doing some profiling.
>
> It's quite possible if he hits the conditional store "optimization"
> (that actually adds unnecessary cache misses) that was recently discussed
> in the load thread safety thread.
Possibly. I'm guessing that what we are actually seeing is something
like an acutely timing-sensitive race condition, where making some
threads faster causes pessimal cache behaviour. It's a really
interesting problem. :-)
Andrew.
--
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903
next prev parent reply other threads:[~2007-11-27 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <474C1A62.9000300@highlandsun.com.suse.lists.egcs>
[not found] ` <18252.8713.124845.847654@zebedee.pink.suse.lists.egcs>
2007-11-27 16:47 ` Andi Kleen
2007-11-27 18:13 ` Andrew Haley [this message]
2007-11-27 15:51 J.C. Pizarro
2007-11-27 20:45 ` Howard Chu
-- strict thread matches above, loose matches on Subject: below --
2007-11-27 14:19 Howard Chu
2007-11-27 14:19 ` Richard Guenther
2007-11-27 16:09 ` Tim Prince
2007-11-27 17:59 ` Howard Chu
2007-11-27 15:46 ` Andrew Haley
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=18252.18256.964029.837816@zebedee.pink \
--to=aph@redhat.com \
--cc=andi@firstfloor.org \
--cc=gcc@gcc.gnu.org \
--cc=hyc@highlandsun.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).