From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: "Frank Ch. Eigler" <fche@redhat.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 07:08:00 -0000 [thread overview]
Message-ID: <3A9BC24D.597BFFAE@cygnus.com> (raw)
In-Reply-To: <200102271425.OAA17433@cam-mail2.cambridge.arm.com>
The ARM simulator doesn't use sim/common so this is strictly a BTW.
sim/common simulators address performance concerns such as function call
overhead using two techniques:
o inline
o compile time
enabling of features
code would we written as:
do_trace_stuff (....)
and then, when the compiler supported it, ``do_trace_stuff'' might or
might not be inlined.
The second bit of trivia relates to Frank's comment. Performance
analysis of simulators has shown that some stuff, like tracing, should
be left as separate functions. The likely reason was that inlining the
code blew out the host CPU cache.
For what it is worth.
Andrew
next prev parent reply other threads:[~2001-02-27 7:08 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
2001-02-27 7:08 ` Andrew Cagney [this message]
[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=3A9BC24D.597BFFAE@cygnus.com \
--to=ac131313@cygnus.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