From: Michael Snyder <msnyder@redhat.com>
To: Joern Rennecke <amylaar@fairadsl.co.uk>
Cc: gdb-patches@sources.redhat.com, joern.rennecke@superh.com,
andrew.stubbs@superh.com
Subject: Re: [RFA] SH4A contribution for sim
Date: Thu, 18 Dec 2003 02:37:00 -0000 [thread overview]
Message-ID: <3FE11300.2090801@redhat.com> (raw)
In-Reply-To: <200312180144.hBI1iosK001449@meolyon.local>
Joern Rennecke wrote:
>>[...] This is why I say that when we are making big changes anyway, we
> should also introduce variable length [01]* bitstring parsing.
> [...]
>
>>through, but I'm thinking that, for instance, "01NN" could be
>>handled in two passes: take the "01" first, then recurse and
>>let the "NN" be handled in the outer switch statement. This
>>might also apply to 01xy and XY01.
>
>
> Yes, that is how I'd like to see this pattern handled. But the '01' can
> bhe handled by code that processes arbitrary length constant bitstrings.
> There is no need to process only specific length of these.
OK, I withdraw this patch, and I will submit a new one that
[only] changes expand_opcode along the lines we have been
discussing. Then I'll submit the rest of this patch separately
(perhaps after further discussion of the movx/movy patterns).
[...]
> I made the movx expansion generate all the combinations of movx with movy
> as well as with nopy. That is this inner loop:
>
> for (m = 0; m < 32; m++)
> {
> /* Ignore illegal nopy */
> if ((m & 7) == 0 && m != 0)
> continue;
> mv = m & 3 | (m & 4) << 2 | (m & 8) << 3 | (m & 16) << 4;
Yes but the h8sx has a bunch of new ones.
We can continue this conversation, I'll separate this change
from the revamp of expand_opcode.
next parent reply other threads:[~2003-12-18 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200312180144.hBI1iosK001449@meolyon.local>
2003-12-18 2:37 ` Michael Snyder [this message]
2003-12-05 2:38 Michael Snyder
2003-12-12 2:40 ` Michael Snyder
2003-12-15 19:03 ` Joern Rennecke
2003-12-17 21:49 ` Michael Snyder
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=3FE11300.2090801@redhat.com \
--to=msnyder@redhat.com \
--cc=amylaar@fairadsl.co.uk \
--cc=andrew.stubbs@superh.com \
--cc=gdb-patches@sources.redhat.com \
--cc=joern.rennecke@superh.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