From: Ben Elliston <bje@redhat.com>
To: gdb@sources.redhat.com
Subject: VPU tracing in simulators
Date: Tue, 20 Feb 2001 20:41:00 -0000 [thread overview]
Message-ID: <14995.18134.253297.130300@scooby.cygnus.com> (raw)
I'd like to propose a new option to the simulator to permit tracing of
VPU instruction semantics. In principle, this follows along from the
idea of tracing FPU instructions and I believe it is sufficiently
general and desirable to be warranted. The details of what will be
traced will be left up to the target.
If there are no objections, I will submit a patch.
Ben
next reply other threads:[~2001-02-20 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 20:41 Ben Elliston [this message]
2001-02-21 8:25 Venkat Natarajan
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=14995.18134.253297.130300@scooby.cygnus.com \
--to=bje@redhat.com \
--cc=gdb@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).