Hi Dann, Yes, that is correct. The i7 core is the Nehalem core basically. Those i3/i5/i7 processors all use the same core I think, just different cache and so on. At least that is my understanding. Either way, we do detect the correct thing.
Bill. On 8 November 2012 23:43, Dann Corbit <dcor...@connx.com> wrote: > I have a Core i7 intel chip. > I assume that Nehalem build is preferred over Core2, since i7 is a descendent > of Nehalem rather than the Xeon core. Is that right? > > -----Original Message----- > From: mpir-devel@googlegroups.com [mailto:mpir-devel@googlegroups.com] On > Behalf Of Bill Hart > Sent: Thursday, November 08, 2012 3:09 PM > To: mpir-devel; sage-de...@googlegroups.com; flint-devel > Subject: [mpir-devel] MPIR 2.6.0 released + appeal for volunteers > > Hi all, > > After a very long alpha/beta release cycle, MPIR 2.6.0 has finally been > released! > > It is available from our website http://mpir.org/ > > This release is dedicated to the memory of Jason Moxham who passed away > recently. > > The main new features in this release are: > > * new FFT implementation for multiplying huge integers > * better support for 64 bit integers on Windows 64 > * Python build generator for MSVC builds > * various bug fixes > > Please report any bugs/success stories on our development list. > > The future of MPIR > ================== > > As a result of the loss of Jason Moxham, the core MPIR development team has > shrunk to two members (there are of course also numerous other developers who > help us test our releases and who submit bug reports every release cycle). > > Brian Gladman and I agree that two core developers is not enough for > sustainable development of MPIR. > Therefore we would like to make an appeal for volunteers to join our team. We > are especially looking to find some talented assembly language programmers > and individuals with experience coding low-level fast arithmetic in C. > > We recognise that there aren't many such people out there, but then again, we > don't need many to take MPIR forward into the future. > > We have also recently decided to switch to using Git for our repository. This > means it will be possible to fork MPIR trivially on GitHub and work in > independent branches. We hope this will make MPIR development more > streamlined. > > We are open to other suggestions about how MPIR might be improved for future > development effort. > > If you are interested in helping out, please contact us on our Google Groups > development list: > > https://groups.google.com/forum/?fromgroups#!forum/mpir-devel > > or email myself or Brian privately. > > Bill Hart. > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to mpir-devel@googlegroups.com. > To unsubscribe from this group, send email to > mpir-devel+unsubscr...@googlegroups.com. > 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 mpir-devel@googlegroups.com. > To unsubscribe from this group, send email to > mpir-devel+unsubscr...@googlegroups.com. > 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 mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
