On Thu, Mar 03, 2022 at 11:16:28AM +0000, Marc Zyngier wrote: > Indeed. The only case where the broken GAS .inst has hit us was in > combination with alternatives (see eb7c11ee3c5c for details). The > encoding itself is always correct, and it is only the label generation > that was broken. If we were affected by this, the kernel would simply > fail to build with these toolchains. > If this ever happens (because we'd add some extra alternative > sequences to the crypto code?), we can revisit this. But in the > meantime, I don't see anything warranting this extra dependency. Ah, in that case the SVE code should be fine too and there's no issue with either. I'd understood the issue to be with the actual instruction encoding.
Attachment:
signature.asc
Description: PGP signature
