qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH v2 23/39] target/i386: introduce instruction


From: Richard Henderson
Subject: Re: [Qemu-devel] [RFC PATCH v2 23/39] target/i386: introduce instruction translator macros
Date: Tue, 13 Aug 2019 07:30:07 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

On 8/10/19 5:12 AM, Jan Bobek wrote:
> +#define CASES_LEG_NP_0F_W0(opcode)              \
> +    case opcode | M_0F | W_0:
> +#define CASES_LEG_NP_0F_W1(opcode)              \
> +    case opcode | M_0F | W_1:
> +#define CASES_LEG_F3_0F_W0(opcode)              \
> +    case opcode | M_0F | P_F3 | W_0:
> +#define CASES_LEG_F3_0F_W1(opcode)              \
> +    case opcode | M_0F | P_F3 | W_1:
> +
> +#define LEG(p, m, w)                            \
> +    CASES_LEG_ ## p ## _ ## m ## _W ## w
> +#define INSN(mnem, cases, opcode, feat)         \
> +    cases(opcode)                               \

It appears as if you don't need the CASES_* macros here.

#define LEG(p, m, w, op) \
   case P_##p | M_##m | W_##2 | op

#define INSN(mnem, leg, feat) \
   leg: translate_insn(env, s, CK_CPUID_##feat, gen_insn(mnem));

so long as P_NP is in the enumeration above with value 0.

Unless there's some other reason that opcode needs to stay separate?


r~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]