From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: strange "a la m32r" comment in cgen-dis.in
Date: Wed, 11 Dec 2002 12:11:00 -0000 [thread overview]
Message-ID: <20021211151108.B16403@redhat.com> (raw)
In-Reply-To: <200212111955.LAA25907@xris-athlon.transmeta.com>; from dje@transmeta.com on Wed, Dec 11, 2002 at 11:55:25AM -0800
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
Hi -
dje wrote:
> 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? [...]
I suspect I was referring to the modifications of buf[]
in cgen/cpu/m32r.opc (my_print_insn).
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-12-11 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 11:55 Doug Evans
2002-12-11 12:11 ` Frank Ch. Eigler [this message]
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=20021211151108.B16403@redhat.com \
--to=fche@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).