public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Greg McGary <greg@mcgary.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sources.redhat.com, sid@sources.redhat.com
Subject: Re: branch probability hinting
Date: Thu, 01 Mar 2001 09:26:00 -0000	[thread overview]
Message-ID: <msae75jt90.fsf@mcgary.org> (raw)
In-Reply-To: <20010301121325.C15190@redhat.com>

"Frank Ch. Eigler" <fche@redhat.com> writes:

> echristo suggests "expect", which I don't like because
> it doesn't have a natural opposite ("unexpect"?).  mrg
> suggests "predict_true". which I don't like because it's
> too verbose.  I like "LIKELY" because it's short,
> eyecatching, and a reversible adjective/adverb that
> suggests a meta-function rather than an ordinary function.
> 
> I'd like to stick with LIKELY/UNLIKELY for now, until
> a better candidate comes along later, riding alongside
> a champion who is eager enough to do the renaming.

I don't normally waste bandwidth with "me too" messages, but since
some expressed their distaste for Frank's naming, I thought I'd offer
some counterweight.  I like Frank's names and capitalization for all
the reasons he explains.  The terminology also meshes with MIPS
jargon.

Greg

      parent reply	other threads:[~2001-03-01  9:26 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
2001-03-01  9:26       ` Greg McGary [this message]

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=msae75jt90.fsf@mcgary.org \
    --to=greg@mcgary.org \
    --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).