From: "Frank Ch. Eigler" <fche@redhat.com>
To: cgen@sources.redhat.com
Subject: Committed rtl.scm change
Date: Mon, 08 Jan 2001 10:47:00 -0000 [thread overview]
Message-ID: <20010108134652.D1879@redhat.com> (raw)
Hi -
I just committed a change to rtl.scm that improves the semantic tracing
messages emitted by the simulators. For the parallel-write case, real
nasty operand names like "h-vr--add-DFLT-const-8--mul-etc-ad-infinitum"
were generated for storage (which is fine) and printed for tracing (not
fine). Now, only the underlying hardware element is printed ("vr"),
plus the index (if any).
I'd like to make the same change to ordinary operand-setting trace messages
too. In specific, for an operand associated with a hardware element, I'd
like to see the hardware name in the semantic trace, not the operand name.
Later, I guess.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6WgscVZbdDOm/ZT0RAg/aAJ9WYrUlqaatVqwBYkmw8UTLULIZpACfaTny
dvVajOA6SGR0zhfxQZfCeuM=
=dwVR
-----END PGP SIGNATURE-----
next reply other threads:[~2001-01-08 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 10:47 Frank Ch. Eigler [this message]
2001-01-08 14:51 ` Ben Elliston
2001-01-08 20:04 ` Frank Ch. Eigler
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=20010108134652.D1879@redhat.com \
--to=fche@redhat.com \
--cc=cgen@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).