From: Richard Henderson <rth@twiddle.net>
To: Andreas Schwab <schwab@suse.de>
Cc: James Antill <james@and.org>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.10-pre11 -- __builtin_expect
Date: Thu, 4 Oct 2001 11:52:04 -0700 [thread overview]
Message-ID: <20011004115204.A11463@twiddle.net> (raw)
In-Reply-To: <20010918031813.57E1062ABC@oscar.casa.dyndns.org.suse.lists.linux.kernel> <E15jBLy-0008UF-00@the-village.bc.nu.suse.lists.linux.kernel> <9o6j9l$461$1@cesium.transmeta.com.suse.lists.linux.kernel> <oup4rq0bwww.fsf_-_@pigdrop.muc.suse.de> <jeelp4rbtf.fsf@sykes.suse.de> <20010918143827.A16003@gruyere.muc.suse.de> <nn3d59qzho.fsf@code.and.org> <jezo7gu78f.fsf@sykes.suse.de> <nnvgi4prod.fsf@code.and.org> <jeofnwsinb.fsf@sykes.suse.de>
In-Reply-To: <jeofnwsinb.fsf@sykes.suse.de>; from schwab@suse.de on Thu, Sep 27, 2001 at 06:28:08PM +0200
On Thu, Sep 27, 2001 at 06:28:08PM +0200, Andreas Schwab wrote:
> You're right, seems like __builtin_expect is really only defined for pure
> boolean values.
I think the documentation mentions the current deficiency in that area.
It is _supposed_ to be defined for all integral and pointer types, but
that is hard with the current built-in infrastructure in the C front end.
r~
next prev parent reply other threads:[~2001-10-04 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010918031813.57E1062ABC@oscar.casa.dyndns.org.suse.lists.linux.kernel>
[not found] ` <E15jBLy-0008UF-00@the-village.bc.nu.suse.lists.linux.kernel>
[not found] ` <9o6j9l$461$1@cesium.transmeta.com.suse.lists.linux.kernel>
2001-09-18 10:44 ` Linux 2.4.10-pre11 -- __builtin_expect Andi Kleen
2001-09-18 11:13 ` Andreas Schwab
2001-09-18 12:38 ` Andi Kleen
2001-09-26 23:54 ` James Antill
2001-09-27 12:51 ` Andreas Schwab
2001-09-27 15:41 ` James Antill
2001-09-27 16:28 ` Andreas Schwab
2001-10-04 18:52 ` Richard Henderson [this message]
2001-10-08 6:17 ` James Antill
2001-09-18 20:11 ` Horst von Brand
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=20011004115204.A11463@twiddle.net \
--to=rth@twiddle.net \
--cc=ak@suse.de \
--cc=james@and.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.