From: Richard Henderson <richard.henderson@linaro.org>
To: "Lucas Mateus Castro(alqotel)" <lucas.araujo@eldorado.org.br>,
qemu-ppc@nongnu.org
Cc: "Joel Stanley" <joel@jms.id.au>,
"Cédric Le Goater" <clg@kaod.org>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [RFC PATCH v2 2/7] target/ppc: Implemented xvi*ger* instructions
Date: Sat, 7 May 2022 22:41:03 -0500 [thread overview]
Message-ID: <c58d0bc1-8f69-e69d-318b-a7bcacf800ff@linaro.org> (raw)
In-Reply-To: <20220506121844.18969-3-lucas.araujo@eldorado.org.br>
On 5/6/22 07:18, Lucas Mateus Castro(alqotel) wrote:
> diff --git a/target/ppc/cpu.h b/target/ppc/cpu.h
> index 10c6d7ae43..348a898950 100644
> --- a/target/ppc/cpu.h
> +++ b/target/ppc/cpu.h
> @@ -238,6 +238,7 @@ typedef union _ppc_vsr_t {
>
> typedef ppc_vsr_t ppc_avr_t;
> typedef ppc_vsr_t ppc_fprp_t;
> +typedef ppc_vsr_t ppc_acc_t;
>
> #if !defined(CONFIG_USER_ONLY)
> /* Software TLB cache */
> diff --git a/target/ppc/helper.h b/target/ppc/helper.h
> index aa6773c4a5..61217e0a10 100644
> --- a/target/ppc/helper.h
> +++ b/target/ppc/helper.h
> @@ -537,6 +537,15 @@ DEF_HELPER_5(XXBLENDVB, void, vsr, vsr, vsr, vsr, i32)
> DEF_HELPER_5(XXBLENDVH, void, vsr, vsr, vsr, vsr, i32)
> DEF_HELPER_5(XXBLENDVW, void, vsr, vsr, vsr, vsr, i32)
> DEF_HELPER_5(XXBLENDVD, void, vsr, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI4GER8, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI4GER8PP, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI8GER4, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI8GER4PP, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI8GER4SPP, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI16GER2, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI16GER2S, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI16GER2PP, void, env, vsr, vsr, vsr, i32)
> +DEF_HELPER_5(XVI16GER2SPP, void, env, vsr, vsr, vsr, i32)
Did you intend to use "acc" here, for documentation purposes?
It's just a couple of #defines above.
Either way, much cleaner.
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2022-05-08 3:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 12:18 [RFC PATCH v2 0/7] VSX MMA Implementation Lucas Mateus Castro(alqotel)
2022-05-06 12:18 ` [RFC PATCH v2 1/7] target/ppc: Implement xxm[tf]acc and xxsetaccz Lucas Mateus Castro(alqotel)
2022-05-08 3:28 ` Richard Henderson
2022-05-06 12:18 ` [RFC PATCH v2 2/7] target/ppc: Implemented xvi*ger* instructions Lucas Mateus Castro(alqotel)
2022-05-08 3:41 ` Richard Henderson [this message]
2022-05-10 17:28 ` Lucas Mateus Martins Araujo e Castro
2022-05-11 0:00 ` Richard Henderson
2022-05-06 12:18 ` [RFC PATCH v2 3/7] target/ppc: Implemented pmxvi*ger* instructions Lucas Mateus Castro(alqotel)
2022-05-08 3:48 ` Richard Henderson
2022-05-12 17:38 ` Lucas Mateus Martins Araujo e Castro
2022-05-06 12:18 ` [RFC PATCH v2 4/7] target/ppc: Implemented xvf*ger* Lucas Mateus Castro(alqotel)
2022-05-08 4:03 ` Richard Henderson
2022-05-09 11:33 ` Lucas Mateus Martins Araujo e Castro
2022-05-06 12:18 ` [RFC PATCH v2 5/7] target/ppc: Implemented xvf16ger* Lucas Mateus Castro(alqotel)
2022-05-08 4:24 ` Richard Henderson
2022-05-10 14:47 ` Lucas Mateus Martins Araujo e Castro
2022-05-06 12:18 ` [RFC PATCH v2 6/7] target/ppc: Implemented pmxvf*ger* Lucas Mateus Castro(alqotel)
2022-05-08 4:25 ` Richard Henderson
2022-05-06 12:18 ` [RFC PATCH v2 7/7] target/ppc: Implemented [pm]xvbf16ger2* Lucas Mateus Castro(alqotel)
2022-05-08 4:27 ` Richard Henderson
2022-05-10 17:25 ` Lucas Mateus Martins Araujo e Castro
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=c58d0bc1-8f69-e69d-318b-a7bcacf800ff@linaro.org \
--to=richard.henderson@linaro.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=joel@jms.id.au \
--cc=lucas.araujo@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).