From: Mark Mitchell <mark@codesourcery.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: trevor_smigiel@playstation.sony.com, gcc <gcc@gcc.gnu.org>,
Russell_Olsen@playstation.sony.com
Subject: Re: __builtin_expect for indirect function calls
Date: Wed, 26 Dec 2007 19:10:00 -0000 [thread overview]
Message-ID: <4772A350.6030907@codesourcery.com> (raw)
In-Reply-To: <20071221220630.Y67443@dair.pair.com>
Hans-Peter Nilsson wrote:
> On Mon, 17 Dec 2007, trevor_smigiel@playstation.sony.com wrote:
>> When we can't hint the real target, we want to hint the most common
>> target. There are potentially clever ways for the compiler to do this
>> automatically, but I'm most interested in giving the user some way to do
>> it explicitly. One possiblity is to have something similar to
>> __builtin_expect, but for functions. For example, I propose:
>>
>> __builtin_expect_call (FP, PFP)
>
> Is there a hidden benefit? I mean, isn't this really
> expressable using builtin_expect as-is, at least when it comes
> to the syntax?
That was my first thought as well. Before we add __builtin_expect_call,
I think there needs to be a justification of why this can't be done with
__builtin_expect as-is.
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2007-12-26 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 0:52 trevor_smigiel
2007-12-18 2:27 ` Jonathan Adamczewski
2007-12-22 3:42 ` Hans-Peter Nilsson
2007-12-26 19:10 ` Mark Mitchell [this message]
2008-01-03 23:36 ` trevor_smigiel
2008-01-05 5:44 ` Mark Mitchell
2008-01-05 10:40 ` Richard Guenther
2008-01-06 19:44 ` Mark Mitchell
2008-01-07 21:15 ` Mark Mendell
2008-01-08 15:36 ` Dave Korn
2008-01-08 15:51 ` Dave Korn
2008-01-03 23:46 ` trevor_smigiel
2008-01-06 20:42 Ross Ridge
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=4772A350.6030907@codesourcery.com \
--to=mark@codesourcery.com \
--cc=Russell_Olsen@playstation.sony.com \
--cc=gcc@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=trevor_smigiel@playstation.sony.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).