auxv + neon

Peter Maydell peter.maydell at linaro.org
Tue Sep 6 15:24:32 UTC 2011


On 6 September 2011 16:09, Andy Doan <andy.doan at linaro.org> wrote:
> On 09/05/2011 11:35 AM, Christian Robottom Reis wrote:
>> On Sat, Sep 03, 2011 at 09:10:58PM +0800, Jim Huang wrote:
>>> 2011/9/3 Tom Gall <tom.gall at linaro.org>:
>>>> Is a method via the aux vectors to know at runtime if neon is or is
>>>> not present?
>>>
>>> hi Tom,
>>>
>>> Did you mean this?
>>>     https://bugs.meego.com/show_bug.cgi?id=12448
>>
>> The recipe in step #1 is probably a good candidate for a FAQ on "How do
>> I tell what features the ARM CPU on my device has?".
>
> done:
>
>  https://wiki.linaro.org/Resources/HowTo/DeterminingNeon

For random "user at the command line" usage is this any better
than the simpler "grep neon /proc/cpuinfo" ? (For that specific
meego bug it serves a purpose in that it reveals that the
libc/auxv is lying, but in general cpuinfo and auxv should
I agree I think.)

If you're a program, you do want to use auxv I think, but
you'd just read it directly rather than invoking an external
binary via the shell to get the dynamic linker to read auxv
for you as a side effect...

-- PMM



More information about the linaro-dev mailing list