tches@gcc.gnu.org
> > Cc: Richard Sandiford ; Mark Rutland
> >
> > Subject: [PATCH 1/1] aarch64: Adapt unwinder to linux's SME signal behaviour
> >
> > From: Richard Sandiford
> >
> > SME uses a lazy save system to manage ZA. The idea is that,
>
> -Original Message-
> From: Richard Sandiford
> Sent: Tuesday, July 15, 2025 9:41 AM
> To: Tamar Christina
> Cc: Yury Khrustalev ; gcc-patches@gcc.gnu.org; Mark
> Rutland
> Subject: Re: [PATCH 1/1] aarch64: Adapt unwinder to linux's SME signal
> behaviour
Tamar Christina writes:
> One question I did have not directly related to the unwinder changes,
> But the ABI mentions that if any of the reserved bytes in TPIDR2_EL0
> Block are non-zero that TPIDR2_EL0 must be left unchanged [1].
The full requirement is:
If TPIDR2_EL0 is nonnull and if any r
: [PATCH 1/1] aarch64: Adapt unwinder to linux's SME signal behaviour
>
> From: Richard Sandiford
>
> SME uses a lazy save system to manage ZA. The idea is that,
> if a function with ZA state wants to call a "normal" function,
> it can leave its state in ZA and
From: Richard Sandiford
SME uses a lazy save system to manage ZA. The idea is that,
if a function with ZA state wants to call a "normal" function,
it can leave its state in ZA and instead set up a lazy save buffer.
If, unexpectedly, that normal function contains a nested use of ZA,
that nested u
