On Mon, Sep 05, 2011 at 11:10:10AM +0100, Peter Maydell wrote:
On 5 September 2011 10:52, Marcin Juszkiewicz
marcin.juszkiew...@linaro.org wrote:
W dniu 05.09.2011 11:28, Andrew Stubbs pisze:
Next question ... is /proc/cpuinfo really the best way to detect this?
I mean, is auxv a better
On Wednesday 07 September 2011 10:32:27 Dave Martin wrote:
Note that the hwcaps info in /proc/cpuinfo is generated from the same
hwcaps word exposed via auxv so, for now, the information is identical.
I would normally rate parsing /proc/cpuinfo as being a bad idea, but
/proc/cpuinfo is
On 01/09/11 10:40, Andrew Stubbs wrote:
I'm currently trying to get GCC to auto-detect what CPU to optimize for
by finding out what CPU it's actually running on (the user would only
have to pass -mcpu=native). It does this simply by reading /proc/cpuinfo.
Thanks to everybody who answered my
W dniu 05.09.2011 11:28, Andrew Stubbs pisze:
Next question ... is /proc/cpuinfo really the best way to detect this?
I mean, is auxv a better approach? Or something else? What's the most
efficient, and most stable API to read the CPU architecture, CPU model,
and FPU/NEON availability?
On 5 September 2011 10:52, Marcin Juszkiewicz
marcin.juszkiew...@linaro.org wrote:
W dniu 05.09.2011 11:28, Andrew Stubbs pisze:
Next question ... is /proc/cpuinfo really the best way to detect this?
I mean, is auxv a better approach? Or something else? What's the most
efficient, and most
W dniu 02.09.2011 06:40, David Brown pisze:
Processor : ARMv7 Processor rev 1 (v7l)
BogoMIPS: 191.69
Features: swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part: 0xc05
CPU revision: 1
Hi all,
I'm currently trying to get GCC to auto-detect what CPU to optimize for
by finding out what CPU it's actually running on (the user would only
have to pass -mcpu=native). It does this simply by reading /proc/cpuinfo.
The problem is finding what magic numbers correspond to what CPU.
If you search the specs on http://infocenter.arm.com for Main ID
register you should get all the numbers you wish for :-)
Apparently it's called ID Code Register for ARM9 and the expected (not
tested ;-) values would be:
ARM926 - 0x926
ARM946 - 0x946
ARM966 - 0x966
etc., you get the picture
W dniu 01.09.2011 12:20, Pawel Moll pisze:
Does anybody have a list of such numbers?
ARM926 - 0x926 (atmel at91sam9263)
ARM920 - 0x920 (atmel at91rm9200)
I have some armv4t/v5t/v6 systems here but none of them under power.
___
linaro-dev mailing list
I actually did look for a bit and never found a definitive list. I've
found descriptions of the bitfield and some sample values, but I haven't
seen an actual official list.
That's correct, I don't think such a list exists (at least within
official ARM specs). What I meant is searching for the
On 1 September 2011 10:40, Andrew Stubbs a...@codesourcery.com wrote:
Hi all,
I'm currently trying to get GCC to auto-detect what CPU to optimize for by
finding out what CPU it's actually running on (the user would only have to
pass -mcpu=native). It does this simply by reading /proc/cpuinfo.
On 1 September 2011 12:02, Pawel Moll pawel.m...@arm.com wrote:
If you search the specs on http://infocenter.arm.com for Main ID
register you should get all the numbers you wish for :-)
Apparently it's called ID Code Register for ARM9 and the expected (not
tested ;-) values would be:
ARM926
On 01/09/11 12:02, Pawel Moll wrote:
If you search the specs on http://infocenter.arm.com for Main ID
register you should get all the numbers you wish for :-)
Apparently it's called ID Code Register for ARM9 and the expected (not
tested ;-) values would be:
Thanks Paweł, this is exactly the
On Thu, Sep 01, 2011 at 10:40:27AM +0100, Andrew Stubbs wrote:
I'm currently trying to get GCC to auto-detect what CPU to optimize
for by finding out what CPU it's actually running on (the user would
only have to pass -mcpu=native). It does this simply by reading
/proc/cpuinfo.
The problem
14 matches
Mail list logo
