From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ben Elliston <bje@redhat.com>
Cc: CGEN <cgen@sources.redhat.com>
Subject: Re: [RFA] Code gen improvement for sim-decode.scm
Date: Wed, 06 Dec 2000 17:36:00 -0000 [thread overview]
Message-ID: <20001206203617.C14971@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012062338170.12462-100000@moshpit.cygnus.com>
Hi -
On Wed, Dec 06, 2000 at 11:40:18PM +1100, Ben Elliston wrote:
: The following patch improves the generated extraction code -- such that an
: `insn' variable is not defined for instructions that have zero ifields.
: [...]
Are you convinced that nothing can possibly use that variable
except ifield extraction? Is the improvement to generated code
merely the removal of a gcc warning? (It should be able to
zap an unused variable, resulting in no performance difference.)
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6LumRVZbdDOm/ZT0RAsT+AJ9jjaI6pCyUw7ASE3CppAUI6DmqHwCcCB2+
OeT+D/iC9Q1Xm1ePIvynAH4=
=06so
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2000-12-06 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 4:40 Ben Elliston
2000-12-06 17:36 ` Frank Ch. Eigler [this message]
2000-12-06 17:44 ` Ben Elliston
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=20001206203617.C14971@redhat.com \
--to=fche@redhat.com \
--cc=bje@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).