On Monday 05 December 2011 02:47:33 Dima Pasechnik wrote:
> On Sunday, December 4, 2011 5:12:21 PM UTC+8, jason wrote:
> > On Sunday 04 December 2011 08:50:21 Volker Braun wrote:
> > > When I tracked down the yasm bug I made a trac ticket at
> > > http://trac.sagemath.org/sage_trac/ticket/11844
> >
On Sunday, December 4, 2011 5:12:21 PM UTC+8, jason wrote:
>
> On Sunday 04 December 2011 08:50:21 Volker Braun wrote:
> > When I tracked down the yasm bug I made a trac ticket at
> > http://trac.sagemath.org/sage_trac/ticket/11844
> >
> > On Saturday, December 3, 2011 11:54:03 PM UTC, jason wro
On Tuesday 25 October 2011 10:43:38 Cactus wrote:
> The issue of 32/64-bit integers on Windows comes up regularly and, after
> the recent discussion, I have been wondering if there is a
> relatively easy implementation strategy.
>
> Since we already know from 64-bit Unix/Linux distributions that t
Hi
I've upgraded yasm to the latest , this fixes a race condition in cygwin and
possibly elsewhere and a few other mnor bits.
I've done the tuning for these cpu's
for x64 arch 64bit ABI only
k8 k102 bobcat netburst core2 penryn nehalem sandybridge atom
and as these are very similar to the abov
On Sunday 04 December 2011 08:50:21 Volker Braun wrote:
> When I tracked down the yasm bug I made a trac ticket at
> http://trac.sagemath.org/sage_trac/ticket/11844
>
> On Saturday, December 3, 2011 11:54:03 PM UTC, jason wrote:
> > > This look like yasm is failing because your doing a parallel bu
On Tuesday 08 November 2011 16:44:19 Bob Smith wrote:
> On 11/4/2011 8:01 PM, Marc wrote:
> > On Nov 5, 12:23 am, Bob Smith wrote:
> >> Using MPIR 2.4.0, I'm substituting my own memory allocator which gets
> >> called from tal-reent.c in __gmp_tmp_reentrant_alloc. The code in that
> >> function d
