From: Andrew Cagney <ac131313@cygnus.com>
To: cgd@broadcom.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [applied mips sim patch] Use igen-generated opcode fields
Date: Mon, 04 Mar 2002 08:03:00 -0000 [thread overview]
Message-ID: <3C8252F5.9060106@cygnus.com> (raw)
In-Reply-To: <yov5bse6wg2e.fsf@broadcom.com>
> "why do it by hand when igen does it for you?"
>
> I believe this addresses (most of) the comment at the top of the file:
>
> // In mips.igen, the semantics for many of the instructions were created
> // using code generated by gencode. Those semantic segments could be
> // greatly simplified.
>
> but i'm not quite sure. Any comments?
Ya! Thanks.
Andrew
> I ran a combined tree built for target mips64-elf through check-gcc
> check-gdb check-sim, and verified that there were no changes in the
> tests from a clean tree.
>
>
>
prev parent reply other threads:[~2002-03-04 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-02 18:17 cgd
2002-03-04 8:03 ` Andrew Cagney [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=3C8252F5.9060106@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cgd@broadcom.com \
--cc=gdb-patches@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