From: Doug Evans <dje@transmeta.com>
To: fche@redhat.com
Cc: cgen@sources.redhat.com, binutils@sources.redhat.com
Subject: strange "a la m32r" comment in cgen-dis.in
Date: Wed, 11 Dec 2002 11:55:00 -0000 [thread overview]
Message-ID: <200212111955.LAA25907@xris-athlon.transmeta.com> (raw)
I don't understand the "possibly modified" part of this comment.
cgen-dis.in:
/* Fill in ex_info fields like read_insn would. Don't actually call
read_insn, since the incoming buffer is already read (and possibly
modified a la m32r). */
Can you elaborate?
A pointer to the place that possibly modifies the incoming buffer
is sufficient. My poor eyes can't find it.
next reply other threads:[~2002-12-11 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 11:55 Doug Evans [this message]
2002-12-11 12:11 ` Frank Ch. Eigler
2002-12-11 12:53 ` Doug Evans
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=200212111955.LAA25907@xris-athlon.transmeta.com \
--to=dje@transmeta.com \
--cc=binutils@sources.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).