I added a basic script and some examples, plus some notes, to trac ticket 8048.
Jason On Thu, Jul 15, 2010 at 4:13 PM, Jason B Hill <[email protected]>wrote: > > This processor actually appears to be 64-bit capable, due to the "lm" > (long-mode) flag. > > I confirmed this via the following link: > http://ark.intel.com/Product.aspx?id=33916 > > Thanks though. Any testing is good testing. > > Jason > > > > On Thu, Jul 15, 2010 at 3:51 PM, John Cremona <[email protected]>wrote: > >> j...@ubuntu%cat /proc/cpuinfo | grep "flags" | uniq >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca >> cmov >> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm >> constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 >> ssse3 cx16 xtpr sse4_1 lahf_lm ida >> >> >> processor : 0 >> vendor_id : GenuineIntel >> cpu family : 6 >> model : 23 >> model name : Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz >> >> >> On 15 July 2010 22:44, Jason B Hill <[email protected]> wrote: >> > >> > I only have access to 64-bit processors. (My 32-bit machine was recently >> > stolen.) Can someone with a 32-bit processor (not just the OS, I need >> the >> > hardware itself to only support 32-bit) running any flavor of Linux >> please >> > copy and paste the result of the following shell command? >> > >> > $ cat /proc/cpuinfo | grep "flags" | uniq >> > >> > Thanks. >> > >> > I should have a testing version for at least Linux, and probably >> Solaris, by >> > the end of the day. >> > >> > Cheers, >> > Jason >> > >> > >> > >> > >> > On Thu, Jul 1, 2010 at 2:55 PM, Peter Jeremy <[email protected]> >> wrote: >> >> >> >> On 2010-Jul-01 13:09:30 -0600, "Jason B. Hill" <[email protected]> >> >> wrote: >> >> >What are others' thoughts on this? I can do a script as well, but only >> >> > for >> >> >Linux. I am also wondering how one would sort by OS, since it is my >> >> >understanding that the main identifier (uname) is about as consistent >> >> >between platforms as /etc/issue is between linux distros. >> >> >> >> I'd also prefer a shellscript because it has no dependencies on the >> >> sage build process. uname is defined by POSIX so it should be >> >> possible to get general output using system-independent code (though >> >> the actual strings reported may vary from OS to OS). CPU and memory >> >> information is more OS-dependent but it shouldn't be too difficult to >> >> write a script (with system-dependent bits) to extract this >> >> information. >> >> >> >> -- >> >> Peter Jeremy >> > >> > -- >> > To post to this group, send an email to [email protected] >> > To unsubscribe from this group, send an email to >> > [email protected]<sage-devel%[email protected]> >> > For more options, visit this group at >> > http://groups.google.com/group/sage-devel >> > URL: http://www.sagemath.org >> > >> >> -- >> To post to this group, send an email to [email protected] >> To unsubscribe from this group, send an email to >> [email protected]<sage-devel%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/sage-devel >> URL: http://www.sagemath.org >> > > -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
