Re: [PATCH v2 2/7] gdb/aarch64: Add custom printing for POR_EL0

[Ezra Sitorus <ezra.sitorus@arm.com>]

> The approach you suggested above is actually what I used in v1
> (https://sourceware.org/pipermail/gdb-patches/2026-June/228082.html).
> With that approach, I was able to display the custom string for
> info registers, info all-registers, and print $por_el0.
> 
> However, the problem I faced was when the register type was por_flags.
> In that case, "set $por_el0 = <value>" failed with an "Invalid case" error.
> Because of this, I had to drop support for writing to por_el0 in the initial
> version of the patch.
> 
> When I tried to resolve this, the only approach I found was to use
> type="uint64_t" so that set works and I have implement the custom string
> handling specifically for info register $por_el0. The downside is that this does
> not affect print $por_el0.

Your v1 version/Thiago's suggestion seems to be what I did for fpmr.  I'm not
sure how it's different than the fpmr case - there's even a test case where I
check writing to fpmr as well: gdb/testsuite/gdb.arch/aarch64-fpmr.exp. This
seems just like the test you have in the patch no. 7 tests.

I'll try to test out your new patch series with the XML version. The previous
version didn't have store_poeregs_to_thread.

Ezra