Re: [PATCH 3/3] aarch64: Avoid redundant writes to FPMR

> On 22 Jan 2025, at 13:53, Richard Sandiford wrote: > > Kyrylo Tkachov writes: >> Hi Richard, >> >>> On 22 Jan 2025, at 13:21, Richard Sandiford >>> wrote: >>> >>> GCC 15 is the first release to support FP8 intrinsics. >>> The underlying instructions depend on the value of a new register,

Re: [PATCH 3/3] aarch64: Avoid redundant writes to FPMR

Kyrylo Tkachov writes: > Hi Richard, > >> On 22 Jan 2025, at 13:21, Richard Sandiford >> wrote: >> >> GCC 15 is the first release to support FP8 intrinsics. >> The underlying instructions depend on the value of a new register, >> FPMR. Unlike FPCR, FPMR is a normal call-clobbered/caller-save >

Re: [PATCH 3/3] aarch64: Avoid redundant writes to FPMR

Hi Richard, > On 22 Jan 2025, at 13:21, Richard Sandiford wrote: > > GCC 15 is the first release to support FP8 intrinsics. > The underlying instructions depend on the value of a new register, > FPMR. Unlike FPCR, FPMR is a normal call-clobbered/caller-save > register rather than a global regis

[PATCH 3/3] aarch64: Avoid redundant writes to FPMR

GCC 15 is the first release to support FP8 intrinsics. The underlying instructions depend on the value of a new register, FPMR. Unlike FPCR, FPMR is a normal call-clobbered/caller-save register rather than a global register. So: - The FP8 intrinsics take a final uint64_t argument that specifie