On Wednesday, 7 October 2015 20:05:11 UTC+2, bluescarni wrote: > > Practically, it's an architecture that supports "natively" 64 bit ints but > the pointers are 32 bits wide. AFAIK, this is supposed to improve > performance for pointer-heavy workloads that do not need to allocate much > RAM but still benefit from the 64 bit ints. >
I could be wrong, but this doesn't sound like it includes SageMath. :-) > > On 7 October 2015 at 19:54, Bill Hart <goodwi...@googlemail.com > <javascript:>> wrote: > >> Actually, now I'm not even sure I understand what x32 is. >> >> I looked it up and found this page and found considerable disagreement on >> what it is: >> >> >> http://stackoverflow.com/questions/7635013/difference-between-x86-x32-and-x64-architectures >> >> I think I'll give it a miss for a while. >> >> Bill. >> >> On Wednesday, 7 October 2015 19:03:18 UTC+2, Bill Hart wrote: >>> >>> >>> >>> On Wednesday, 7 October 2015 18:37:41 UTC+2, Jean-Pierre Flori wrote: >>>> >>>> >>>> >>>> On Wednesday, October 7, 2015 at 6:35:36 PM UTC+2, bluescarni wrote: >>>>> >>>>> >>>>>>> * PARI which assumes that sizeof(long) == sizeof(void*), there is an >>>>>>> experimental branch fixing this: >>>>>>> http://pari.math.u-bordeaux.fr/archives/pari-dev-1505/msg00021.html >>>>>>> >>>>>> >>>>>> I am using Pari (not GP) today on Windows 64. It was minimal effort >>>>>> on my part to do so. I am not using a special branch. >>>>>> >>>>> >>>>> This was a problem for the x32 architecture as well. See, e.g., here: >>>>> >>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724320 >>>>> >>>>> Glad that the PARI devs fixed this eventually. >>>>> >>>> It was not fixed by an "actual" PARI dev, but what's important is that >>>> some code is now publicly available. >>>> >>> >>> I read through that entire Debian issue and still haven't got a clue >>> what the issue was. There seems to have been a lot of arguing there about >>> whose fault this actually was. None of these people is a dummy, so I don't >>> understand why they couldn't figure it out. >>> >>> Anyway, x32 is not something I'm interested in supporting. It's great >>> that GMP does, and some other software does, and Flint is moving towards >>> supporting it. But it's not a priority. >>> >>> Bill. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-devel+...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-...@googlegroups.com >> <javascript:>. >> Visit this group at http://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
