On 30/04/2021 15:43, Richard Henderson wrote:
On 4/30/21 11:02 AM, Matheus K. Ferst wrote:
But in this case ADDI probably doesn't use PLS_D. You could use
static bool trans_PADDI(DisasContext *ctx, arg_PLS_D *a) { arg_D
d; if (!resolve_PLS_D(ctx, , a)) { return false; } return
On 4/30/21 1:32 PM, Luis Fernando Fujita Pires wrote:
From: Richard Henderson
On 4/30/21 11:45 AM, Luis Fernando Fujita Pires wrote:
I think we can already pass multiple files to decodetree.py and it will handle
them correctly. I just didn't find a way to do that from the meson build files,
From: Richard Henderson
> On 4/30/21 11:45 AM, Luis Fernando Fujita Pires wrote:
> > I think we can already pass multiple files to decodetree.py and it will
> > handle
> them correctly. I just didn't find a way to do that from the meson build
> files,
> which assume decodetree will always use a
On 4/30/21 11:45 AM, Luis Fernando Fujita Pires wrote:
I think we can already pass multiple files to decodetree.py and it will handle
them correctly. I just didn't find a way to do that from the meson build files,
which assume decodetree will always use a single input file.
Oh, riscv does
On 4/30/21 11:02 AM, Matheus K. Ferst wrote:
But in this case ADDI probably doesn't use PLS_D. You could use
static bool trans_PADDI(DisasContext *ctx, arg_PLS_D *a)
{
arg_D d;
if (!resolve_PLS_D(ctx, , a)) {
return false;
}
return trans_ADDI(ctx, );
}
making sure
From: Richard Henderson
> On 4/30/21 4:23 AM, Luis Fernando Fujita Pires wrote:
> > I think we should reconsider using the same .decode file for both 32-
> > and 64-bit instructions, to avoid duplicating argument set
> > definitions, and to keep the prefixed instructions close to their
> >
On 30/04/2021 11:31, Richard Henderson wrote:
On 4/30/21 7:05 AM, Matheus K. Ferst wrote:
+ADDI 01 10 0--.-- .. \
+ 001110 . . @PLS_D
I'm not sure about this. It's a bit surprising to find ADDI here, and
the
On 4/30/21 7:05 AM, Matheus K. Ferst wrote:
+ADDI 01 10 0--.-- .. \
+ 001110 . . @PLS_D
I'm not sure about this. It's a bit surprising to find ADDI here, and the
comment that explains why is likely to be ignored
On 4/30/21 4:23 AM, Luis Fernando Fujita Pires wrote:
I think we should reconsider using the same .decode file for both 32- and
64-bit instructions, to avoid duplicating argument set definitions, and to
keep the prefixed instructions close to their non-prefixed counterparts.
varinsnwidth assumes
On 29/04/2021 22:15, Richard Henderson wrote:
Signed-off-by: Richard Henderson
---
target/ppc/insn32.decode | 12 +++
target/ppc/insn64.decode | 15 +
target/ppc/translate.c | 29
Signed-off-by: Richard Henderson
---
target/ppc/insn32.decode | 12 +++
target/ppc/insn64.decode | 15 +
target/ppc/translate.c | 29
target/ppc/translate/fixedpoint-impl.c.inc | 39 ++
4
11 matches
Mail list logo
