Re: libatomic: use HWCAPs in AArch64 ifunc tests

2025-03-13 Thread Richard Sandiford
Wilco Dijkstra writes: > Hi Richard, > >> Could you give details?  I thought it was always known that trapped >> system register accesses were slow.  In the previous versions, the >> checks seemed to be presented as an up-front price worth paying for >> faster atomic operations, on the systems tha

Re: libatomic: use HWCAPs in AArch64 ifunc tests

2025-03-13 Thread Wilco Dijkstra
Hi Richard, > Could you give details?  I thought it was always known that trapped > system register accesses were slow.  In the previous versions, the > checks seemed to be presented as an up-front price worth paying for > faster atomic operations, on the systems that would use those paths. > Now

Re: libatomic: use HWCAPs in AArch64 ifunc tests

2025-03-04 Thread Richard Sandiford
Wilco Dijkstra writes: > Feedback from the kernel team suggests that it's best to only use HWCAPs > rather than also use low-level checks as done by has_lse128() and has_rcpc3(). > So change these to just use HWCAPs which simplifies the code and speeds up > ifunc selection by avoiding expensive sy

libatomic: use HWCAPs in AArch64 ifunc tests

2025-03-03 Thread Wilco Dijkstra
Feedback from the kernel team suggests that it's best to only use HWCAPs rather than also use low-level checks as done by has_lse128() and has_rcpc3(). So change these to just use HWCAPs which simplifies the code and speeds up ifunc selection by avoiding expensive system register accesses. Passes