Re: [PATCH] arm: Don't require a runtime check function for targets with unconditional NEON
Cosmin Truta <[email protected]> Tue, 11 Oct 2022 16:36:51 +0300
| Newsgroups | gmane.comp.graphics.png.devel |
|---|---|
| Message-ID | <CAAoVtZzmQ-794nGQ5mHvves7+-vLz+Y5Jzeiy-2v=HE6VFEM5w@mail.gmail.com> |
On Tue, Oct 11, 2022 at 4:30 PM Cosmin Truta <[email protected]> wrote: > > Actually, I think I'm having a change of mind: > > A developer may enable the __ARM_NEON__ codegen at compile time, but > that is not necessarily an assurance that the intended target machine > (to be used at run time) is actually Neon-enabled. D'oh! I take this back. I think that you, Martin, are correct to say that __ARM_NEON__ is an indication that the compiler may liberally insert ARM Neon code anywhere, which further means that checking for ARM Neon hardware availability at run time is futile. I need to study this more. > On the other hand, I do agree that the configure script and the cmake > file should be consistent in their behavior. ... but I do stand behind this other statement. Sincerely, Cosmin