From: Richard Earnshaw <rearnsha@arm.com>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: Richard.Earnshaw@arm.com, DJ Delorie <dj@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch] add trace capabilities to arm sim
Date: Tue, 27 Feb 2001 06:26:00 -0000 [thread overview]
Message-ID: <200102271425.OAA17433@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: <o53dd1w76u.fsf@toenail.toronto.redhat.com>
>
> Richard Earnshaw <rearnsha@arm.com> writes:
>
> : I haven't seen anyone else comment on this, so I'll stick my nose in ;-)
> : I can't approve or reject this patch, but:
>
> Thanks - your input is always appreciated.
>
>
> : [...]
> : > if (state->Exception)
> : > { /* Any exceptions */
> :
> : and then bump state->Exception (which behaves pretty much like a semaphore
> : count on the number of extra things to go look at) when tracing needs to
> : run.
>
> An interesting technique! Have you tried using gcc's __builtin_expect
> function to provide branch (un)likelihood hints to the compiler,
> instead of this method?
Well, it would have a marginal benefit on those hosts that support branch
prediction, but you would still need to do each check. As long as we
don't get to the point where state->Exception is more often true than
false, it is still a benefit to wrap them all up into a single pre-check.
R.
next parent reply other threads:[~2001-02-27 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <o53dd1w76u.fsf@toenail.toronto.redhat.com>
2001-02-27 6:26 ` Richard Earnshaw [this message]
2001-02-27 7:08 ` Andrew Cagney
[not found] <200102240025.TAA28612@greed.delorie.com>
2001-02-26 10:40 ` Richard Earnshaw
2001-02-26 10:57 ` DJ Delorie
2001-02-26 11:02 ` Richard Earnshaw
2001-02-26 11:12 ` DJ Delorie
2001-02-27 1:47 ` Richard Earnshaw
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=200102271425.OAA17433@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=dj@redhat.com \
--cc=fche@redhat.com \
--cc=gdb-patches@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