From: Ben Elliston <bje@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: CGEN <cgen@sources.redhat.com>
Subject: Re: [RFA] Code gen improvement for sim-decode.scm
Date: Wed, 06 Dec 2000 17:44:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.31.0012071242340.15613-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <20001206203617.C14971@redhat.com>
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.)
Nothing else can use it because it's defined within block scope. Yes, the
improvement to generated code is to remove a GCC warning.
Ben
prev parent reply other threads:[~2000-12-06 17:44 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
2000-12-06 17:44 ` Ben Elliston [this message]
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=Pine.LNX.4.31.0012071242340.15613-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).