StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>These values come from a Linux structure. They can be displayed from a shell by <code>cat /proc/cpuinfo</code>. The ARM defines them in the <code>arch/arm/mm</code> directory. From this directory,</p> <pre><code>grep cpu_arch_name * | grep string | cut -d \, -f2 | sort | uniq </code></pre> <ul> <li>armv4</li> <li>armv4t</li> <li>armv5t</li> <li>armv5te</li> <li>armv5tej</li> <li>armv6</li> <li>armv7</li> </ul> <p>The <em>arm7l</em> indicates "little endian" mode, but this is selectable and depends on the kernel. I would think most ARM kernels will be "little endian", unless it is a network centric product (like an Android router). This is the same as <code>uname -m</code>. On the x86, it returns "i686" on a PowerPC, it returns "ppc". I don't have a MIPS system, but my guess is "mips", but it could be the assortment found in <a href="https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/mips/kernel/cpu-probe.c" rel="nofollow noreferrer"><strong>cpu-probe.c</strong></a></p> <p>There are over 20 architectures in Linux all with different CPU versions. The answer is far less for current Android ports. However, it is possible that any of them can be used in the future. I think that the ARM is the only one sending a <em>sub-architechure</em>.</p> <p>See also: <a href="http://man7.org/linux/man-pages/man2/uname.2.html" rel="nofollow noreferrer"><code>uname()</code> man page</a>, <a href="http://en.wikipedia.org/wiki/Uname" rel="nofollow noreferrer">Wikipedia's <em>Uname</em></a>, <a href="https://serverfault.com/questions/63484/linux-what-are-the-possible-values-returned-by-uname-m-and-uname-p">Server faults's uname machines</a>, <a href="http://marc.info/?l=openjdk-jdk8-dev&m=135796746534007&w=1" rel="nofollow noreferrer">OpenJdk mailing list</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload