Alexandre Oliva <ol...@adacore.com> writes: > On Jan 23, 2024, Richard Sandiford <richard.sandif...@arm.com> wrote: > >> Performing the check in expand is itself wrong > > *nod* > >> So I think we should enforce the immediate range within the frontend >> instead, via TARGET_CHECK_BUILTIN_CALL. > > Sounds good. Can that accommodate the existing uses in always_inline > wrappers?
No, I don't think so. We'd probably need to move them to directly-defined builtins (i.e. defined via handle_arm_neon_h, rather than at start-up). >> Unfortunately that isn't suitable for stage 4 though. > > ACK. Is there a partial implementation of that? I might get a chance > to take it to completion, even if it doesn't make gcc 14. Not that I know of, sorry. Thanks, Richard
