From: Luis Machado <luis.machado@arm.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 01/16] [gdb/aarch64] Fix register fetch/store order for native AArch64 Linux
Date: Mon, 24 Jul 2023 17:26:30 +0100 [thread overview]
Message-ID: <5f63fb04-32c3-e5fe-445e-709c4cdc4f35@arm.com> (raw)
In-Reply-To: <87ila9jofh.fsf@linaro.org>
Hi,
On 7/24/23 16:53, Thiago Jung Bauermann wrote:
>
> Hello Luis,
>
> I'm (slowly) going through your patches. I only found a few small nits
> so far.
Thanks! That will be very helpful.
>
> Luis Machado via Gdb-patches <gdb-patches@sourceware.org> writes:
>
>> @@ -521,28 +522,28 @@ aarch64_fetch_registers (struct regcache *regcache, int regno)
>> if (tdep->has_tls ())
>> fetch_tlsregs_from_thread (regcache);
>> }
>> + /* General purpose register? */
>> else if (regno < AARCH64_V0_REGNUM)
>> fetch_gregs_from_thread (regcache);
>> - else if (tdep->has_sve ())
>> + /* SVE register? */
>> + else if (tdep->has_sve () && regno <= AARCH64_SVE_VG_REGNUM)
>> fetch_sveregs_from_thread (regcache);
>> - else
>> + /* FPSIMD register? */
>> + else if (regno < AARCH64_FPCR_REGNUM)
>
> fetch_fpregs_from_thread reads AARCH64_FPCR_REGNUM, so shouldn't the if
> condition above use '<='?
>
> Ditto for aarch64_store_registers further below.
>
Yes, this does look like a mistake when reworking this code.
>> fetch_fpregs_from_thread (regcache);
>> -
>> - if (tdep->has_pauth ())
>> - {
>> - if (regno == AARCH64_PAUTH_DMASK_REGNUM (tdep->pauth_reg_base)
>> - || regno == AARCH64_PAUTH_CMASK_REGNUM (tdep->pauth_reg_base))
>> - fetch_pauth_masks_from_thread (regcache);
>> - }
>> -
>> - /* Fetch individual MTE registers. */
>> - if (tdep->has_mte ()
>> - && (regno == tdep->mte_reg_base))
>> + /* PAuth register? */
>> + else if (tdep->has_pauth ()
>> + && (regno == AARCH64_PAUTH_DMASK_REGNUM (tdep->pauth_reg_base)
>> + || regno == AARCH64_PAUTH_CMASK_REGNUM (tdep->pauth_reg_base)))
>> + fetch_pauth_masks_from_thread (regcache);
>> + /* MTE register? */
>> + else if (tdep->has_mte ()
>> + && (regno == tdep->mte_reg_base))
>> fetch_mteregs_from_thread (regcache);
>> -
>> - if (tdep->has_tls ()
>> - && regno >= tdep->tls_regnum_base
>> - && regno < tdep->tls_regnum_base + tdep->tls_register_count)
>> + /* TLS register? */
>> + else if (tdep->has_tls ()
>> + && regno >= tdep->tls_regnum_base
>> + && regno < tdep->tls_regnum_base + tdep->tls_register_count)
>> fetch_tlsregs_from_thread (regcache);
>> }
>>
>> @@ -592,6 +593,7 @@ aarch64_store_registers (struct regcache *regcache, int regno)
>> aarch64_gdbarch_tdep *tdep
>> = gdbarch_tdep<aarch64_gdbarch_tdep> (regcache->arch ());
>>
>> + /* Do we need to store all registers? */
>> if (regno == -1)
>> {
>> store_gregs_to_thread (regcache);
>> @@ -606,22 +608,26 @@ aarch64_store_registers (struct regcache *regcache, int regno)
>> if (tdep->has_tls ())
>> store_tlsregs_to_thread (regcache);
>> }
>> + /* General purpose register? */
>> else if (regno < AARCH64_V0_REGNUM)
>> store_gregs_to_thread (regcache);
>> - else if (tdep->has_sve ())
>> + /* SVE register? */
>> + else if (tdep->has_sve () && regno <= AARCH64_SVE_VG_REGNUM)
>> store_sveregs_to_thread (regcache);
>> - else
>> + /* FPSIMD register? */
>> + else if (regno < AARCH64_FPCR_REGNUM)
>
> Shouldn't it be "regno <= AARCH64_FPCR_REGNUM" here?
>
Yes. I'll fix those up. Thanks for spotting those.
>> store_fpregs_to_thread (regcache);
>> -
>> - /* Store MTE registers. */
>> - if (tdep->has_mte ()
>> - && (regno == tdep->mte_reg_base))
>> + /* MTE register? */
>> + else if (tdep->has_mte ()
>> + && (regno == tdep->mte_reg_base))
>> store_mteregs_to_thread (regcache);
>> -
>> - if (tdep->has_tls ()
>> - && regno >= tdep->tls_regnum_base
>> - && regno < tdep->tls_regnum_base + tdep->tls_register_count)
>> + /* TLS register? */
>> + else if (tdep->has_tls ()
>> + && regno >= tdep->tls_regnum_base
>> + && regno < tdep->tls_regnum_base + tdep->tls_register_count)
>> store_tlsregs_to_thread (regcache);
>> +
>> + /* PAuth registers are read-only. */
>> }
>>
>> /* A version of the "store_registers" target_ops method used when running
>
next prev parent reply other threads:[~2023-07-24 16:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 13:46 [PATCH v3 00/16] SME support for AArch64 gdb/gdbserver on Linux Luis Machado
2023-06-30 13:46 ` [PATCH v3 01/16] [gdb/aarch64] Fix register fetch/store order for native AArch64 Linux Luis Machado
2023-07-24 15:53 ` Thiago Jung Bauermann
2023-07-24 16:26 ` Luis Machado [this message]
2023-06-30 13:46 ` [PATCH v3 02/16] [gdb/aarch64] refactor: Rename SVE-specific files Luis Machado
2023-06-30 13:46 ` [PATCH v3 03/16] [gdb/gdbserver] refactor: Simplify SVE interface to read/write registers Luis Machado
2023-07-24 16:19 ` Thiago Jung Bauermann
2023-07-25 9:28 ` Luis Machado
2023-06-30 13:46 ` [PATCH v3 04/16] [gdb/aarch64] sve: Fix return command when using V registers in a SVE-enabled target Luis Machado
2023-06-30 13:46 ` [PATCH v3 05/16] [gdb/aarch64] sme: Enable SME registers and pseudo-registers Luis Machado
2023-07-26 20:01 ` Thiago Jung Bauermann
2023-07-27 9:01 ` Luis Machado
2023-07-28 1:19 ` Thiago Jung Bauermann
2023-06-30 13:46 ` [PATCH v3 06/16] [gdbserver/aarch64] refactor: Adjust expedited registers dynamically Luis Machado
2023-06-30 13:46 ` [PATCH v3 07/16] [gdbserver/aarch64] sme: Add support for SME Luis Machado
2023-07-27 19:41 ` Thiago Jung Bauermann
2023-06-30 13:46 ` [PATCH v3 08/16] [gdb/aarch64] sve: Fix signal frame z/v register restore Luis Machado
2023-07-27 21:52 ` Thiago Jung Bauermann
2023-07-31 12:22 ` Luis Machado
2023-06-30 13:46 ` [PATCH v3 09/16] [gdb/aarch64] sme: Signal frame support Luis Machado
2023-07-27 22:25 ` Thiago Jung Bauermann
2023-07-31 12:23 ` Luis Machado
2023-06-30 13:46 ` [PATCH v3 10/16] [gdb/aarch64] sme: Fixup sigframe gdbarch when vg/svg changes Luis Machado
2023-07-28 1:01 ` Thiago Jung Bauermann
2023-07-31 12:27 ` Luis Machado
2023-06-30 13:46 ` [PATCH v3 11/16] [gdb/aarch64] sme: Support TPIDR2 signal frame context Luis Machado
2023-06-30 13:46 ` [PATCH v3 12/16] [gdb/generic] corefile/bug: Use thread-specific gdbarch when dumping register state to core files Luis Machado
2023-06-30 13:46 ` [PATCH v3 13/16] [gdb/generic] corefile/bug: Fixup (gcore) core file target description reading order Luis Machado
2023-07-28 3:12 ` Thiago Jung Bauermann
2023-07-31 11:38 ` Luis Machado
2023-09-05 8:28 ` Luis Machado
2023-06-30 13:46 ` [PATCH v3 14/16] [gdb/aarch64] sme: Core file support for Linux Luis Machado
2023-08-03 0:18 ` Thiago Jung Bauermann
2023-08-03 11:37 ` Luis Machado
2023-08-04 20:45 ` Thiago Jung Bauermann
2023-06-30 13:46 ` [PATCH v3 15/16] [gdb/testsuite] sme: Add SVE/SME testcases Luis Machado
2023-08-04 0:59 ` Thiago Jung Bauermann
2023-08-11 15:42 ` Luis Machado
2023-08-12 0:42 ` Thiago Jung Bauermann
2023-06-30 13:46 ` [PATCH v3 16/16] [gdb/docs] sme: Document SME registers and features Luis Machado
2023-07-01 8:58 ` Eli Zaretskii
2023-07-03 9:52 ` Luis Machado
2023-07-03 12:03 ` Eli Zaretskii
2023-07-03 12:06 ` Luis Machado
2023-07-17 11:40 ` [PING][PATCH v3 00/16] SME support for AArch64 gdb/gdbserver on Linux Luis Machado
2023-07-24 8:15 ` Luis Machado
2023-08-04 21:24 ` [PATCH " Thiago Jung Bauermann
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=5f63fb04-32c3-e5fe-445e-709c4cdc4f35@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@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 read-only IMAP folder(s) and NNTP newsgroup(s).