From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-devel@nongnu.org
Cc: edgar.iglesias@amd.com
Subject: Re: [PATCH v1 2/4] target/microblaze: div: Rename and reorder function args
Date: Mon, 25 Aug 2025 12:11:25 +0200 [thread overview]
Message-ID: <a879c454-626b-4194-80f2-229ad60ca971@linaro.org> (raw)
In-Reply-To: <80a82610-0423-4e25-a88a-14c4f7d95ed3@linaro.org>
On 25/8/25 01:32, Richard Henderson wrote:
> On 8/25/25 08:27, Edgar E. Iglesias wrote:
>> From: "Edgar E. Iglesias" <edgar.iglesias@amd.com>
>>
>> Rename and reorder function args to better match with spec
>> and pseudo code.
>>
>> No functional change.
>>
>> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@amd.com>
>> ---
>> target/microblaze/op_helper.c | 18 +++++++++---------
>> target/microblaze/translate.c | 12 ++----------
>> 2 files changed, 11 insertions(+), 19 deletions(-)
>>
>> diff --git a/target/microblaze/op_helper.c b/target/microblaze/
>> op_helper.c
>> index 470526ee92..092977b3e1 100644
>> --- a/target/microblaze/op_helper.c
>> +++ b/target/microblaze/op_helper.c
>> @@ -69,9 +69,9 @@ void helper_raise_exception(CPUMBState *env,
>> uint32_t index)
>> cpu_loop_exit(cs);
>> }
>> -static bool check_divz(CPUMBState *env, uint32_t b, uintptr_t ra)
>> +static bool check_divz(CPUMBState *env, uint32_t divisor, uintptr_t pc)
>
> The name GETPC notwithstanding, I don't think ra -> pc is a good rename.
>
> PC often gets confused about whether that's a host or guest value.
> RA (return address) is less so; it gets used often in core tcg.
>
> If you really don't like RA, then perhaps "retaddr" (also with quite a
> bit of usage) or "unwind_pc" (no existing usage, but very descriptive).
+1 for 'unwind_pc'.
While thinking more about it, I noticed we don't document the
prototypes in "exec/cpu-common.h". Doing so we could rename
s/pc/unwind_pc/ and document @unwind_pc. Also these helpers
would be better declared in a TCG specific header. Anyway,
note for Richard, orthogonal to this patch ;)
next prev parent reply other threads:[~2025-08-25 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 22:27 [PATCH v1 0/4] targets/microblaze: Handle signed division overflows Edgar E. Iglesias
2025-08-24 22:27 ` [PATCH v1 1/4] target/microblaze: Remove unused arg from check_divz() Edgar E. Iglesias
2025-08-24 23:27 ` Richard Henderson
2025-08-24 22:27 ` [PATCH v1 2/4] target/microblaze: div: Rename and reorder function args Edgar E. Iglesias
2025-08-24 23:32 ` Richard Henderson
2025-08-25 10:11 ` Philippe Mathieu-Daudé [this message]
2025-08-25 10:58 ` Edgar E. Iglesias
2025-08-24 22:27 ` [PATCH v1 3/4] target/microblaze: Break out raise_divzero() Edgar E. Iglesias
2025-08-24 23:36 ` Richard Henderson
2025-08-25 11:02 ` Edgar E. Iglesias
2025-08-24 22:27 ` [PATCH v1 4/4] target/microblaze: Handle signed division overflows Edgar E. Iglesias
2025-08-24 23:44 ` Richard Henderson
2025-08-25 10:59 ` Edgar E. Iglesias
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=a879c454-626b-4194-80f2-229ad60ca971@linaro.org \
--to=philmd@linaro.org \
--cc=edgar.iglesias@amd.com \
--cc=edgar.iglesias@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).