public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Blechmann <tim@klingt.org>
To: Brian Gerst <brgerst@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] branch hint tweaks
Date: Tue, 24 Nov 2009 19:21:57 +0100	[thread overview]
Message-ID: <4B0C2445.2000008@klingt.org> (raw)
In-Reply-To: <73c1f2160911240950u7256feedqc475fa915dda43ca@mail.gmail.com>

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

> Did you run profiling tests again after making these changes to see if
> they had any effect?  likely() and unlikely() are only hints.  GCC
> doesn't have to follow them, or it could be broken in recent GCC
> versions.

i know, the compiler doesn't have to follow the hint ... but with the
likely/unlikely profiling, not the execution time is profiled, but
whether the branch hint is pointing to the right direction on my machine
... if the assembly is actually affected does probably depend on the
compiler version, instruction set, cpu tuning ...

tim

-- 
tim@klingt.org
http://tim.klingt.org

The aim of education is the knowledge, not of facts, but of values
  William S. Burroughs


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-11-24 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 10:54 [PATCH 0/5] branch hint tweaks Tim Blechmann
2009-11-24 17:50 ` Brian Gerst
2009-11-24 18:17   ` Aaron Cohen
2009-11-24 18:59     ` Brian Gerst
2009-11-24 18:21   ` Tim Blechmann [this message]
2009-11-24 20:13     ` Brian Gerst

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=4B0C2445.2000008@klingt.org \
    --to=tim@klingt.org \
    --cc=brgerst@gmail.com \
    --cc=linux-kernel@vger.kernel.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