From: Greg McGary <greg@mcgary.org>
To: Dave Brolley <brolley@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
cgen@sources.redhat.com, sid@sources.redhat.com
Subject: Re: branch probability hinting
Date: Thu, 01 Mar 2001 09:32:00 -0000 [thread overview]
Message-ID: <ms4rxdjsz3.fsf@mcgary.org> (raw)
In-Reply-To: <3A9E852C.9040702@redhat.com>
Dave Brolley <brolley@redhat.com> writes:
> The problem I have with
>
> if (LIKELY (test))
> ...code...
>
> is that to a casual reader it looks like it's an actual test for
> something which is likely (a heuristic?) rather than an optimization hint.
I generally don't buy such arguments. The casual reader generally
deserves any misunderstandings s/he has. If it's truly casual
reading, then the misunderstandings are inconsequential. If someone
really cares to know what's going on, then it's time to become more
circumspect and track down the definition. This same procedure
applies to zillions of other names in a program that might be
unfamiliar. LIKELY/UNLIKELY is as evocative of its real meaning for
me as some other choice of names is for you. As Abe Lincoln once
said: "You can please some of the people all of the time, you can
please all of the people some of the time, but you can't please all of
the people all of the time."
Greg
next prev parent reply other threads:[~2001-03-01 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 14:35 Frank Ch. Eigler
2001-02-28 15:01 ` Greg McGary
2001-02-28 16:37 ` matthew green
[not found] ` <6863.983407030.cygnus.local.cgen@cygnus.com>
2001-02-28 16:50 ` Eric Christopher
2001-02-28 17:04 ` matthew green
2001-03-01 9:13 ` Frank Ch. Eigler
2001-03-01 9:21 ` Dave Brolley
2001-03-01 9:32 ` Greg McGary [this message]
2001-03-01 9:26 ` Greg McGary
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=ms4rxdjsz3.fsf@mcgary.org \
--to=greg@mcgary.org \
--cc=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.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).