That processor is a nehalem. But I would need to know the family and model from David's CPU, as we should be detecting that correctly. Of course, if the C compiler isn't working....
Anyhow, those are definitely not some kind of core2. Bill. 2010/1/29 Gonzalo Tornaria <[email protected]>: > On Thu, Jan 28, 2010 at 9:00 PM, Bill Hart <[email protected]> > wrote: >> 2010/1/28 Dr. David Kirkby <[email protected]>: >>> I'm using an Intel W3580 - 3.33 GHz Quad core Xeon. >>> >>> http://ark.intel.com/Product.aspx?id=39723 >>> >>> I've seen other packages use something different to both core2 and penryn, >>> and if I recall correctly, the name was some sort of code name used on Xeons >> >> MPIR can only use names for processors corresponding to assembly >> language we've actually written. We've written no special assembly >> language for these particular Xeons, so it uses the best code we have >> available for this processor, which is core2. You are welcome to >> contribute better assembly code for this machine if you want. :-) > > Isn't it a "nehalem" ? > > It seems to have the same cpuid string (106A5h) as mine, which is > correctly detected as nehalem by config.guess (for the record, it's > model 1Ah = 26) > > David, can you confirm > > (a) your cpu is a model 26 > (b) what's the output of ./config.guess > > Best, > Gonzalo > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
