Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rx sim] add decode cache
Date: Fri, 30 Jul 2010 00:17:00 -0000	[thread overview]
Message-ID: <201007300017.o6U0H6lM024851@greed.delorie.com> (raw)
In-Reply-To: <201007291941.18708.vapier@gentoo.org> (message from Mike	Frysinger on Thu, 29 Jul 2010 19:41:17 -0400)


> i havent been able to figure out cgen.  but from what i can see,
> with a complete implementation already, i cant say it's worth the
> effort to move to the cgen infrastructure.

In the case of the m32c, the cgen implementation is *so* complex, that
there's still a few opcodes it doesn't support, and I haven't been
able to figure out how to fix it yet.

CGEN at the time really didn't like variable length opcodes.


  reply	other threads:[~2010-07-30  0:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 18:42 DJ Delorie
2010-07-29 19:23 ` Mike Frysinger
2010-07-29 19:34   ` DJ Delorie
2010-07-29 21:42     ` Mike Frysinger
2010-07-29 22:00       ` DJ Delorie
2010-07-30  0:09         ` Mike Frysinger
2010-07-30  0:17           ` DJ Delorie [this message]
2010-07-30  1:04         ` Kevin Buettner

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=201007300017.o6U0H6lM024851@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.org \
    /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