> There are few cpu's which I think MPIR has not been tested on
>
> mpn/sh see
>
> http://en.wikipedia.org/wiki/SuperH
>
> This architecture has been expanded to 64bit :) , but the only asm
> code MPIR has is sh2 which is used in automotive apps :(
>
> mpn/m68k see
>
> http://en.wikipedia.org
On Wednesday 06 July 2011 00:29:51 Jason wrote:
> Hi
>
> something interesting , comparing MPIR svn against another popular lib ,
> mul time in cycles for MPIR and the slowdown for the other lib
>
>
> 8 #184.021.0730
> 9 #232.031.1587
> 10#278.
Hi
something interesting , comparing MPIR svn against another popular lib , mul
time in cycles for MPIR and the slowdown for the other lib
8 #184.021.0730
9 #232.031.1587
10#278.041.1292
11#329.041.1178
12
On Tuesday 05 July 2011 17:57:40 Jason wrote:
> On Tuesday 05 July 2011 17:14:41 Cactus wrote:
> > Are you using the AMD code on the Intel Architectures?
> >
> > Brian
>
> Yep
> K8 version on K8,core2,atom,netburst
> K10 version on nehalem,sandybridge,bobcat
>
> and I'll tweek the core2 vers
On Jul 5, 8:11 pm, Cactus wrote:
> Optimisation of assembler code for Windows x64 within prologue and epilogue
> code is pretty heavily constrained by the calling conventions so some of
> your changes between versions don't carry across to Windows.
>
> In particular, unless a frame pointer is decl
Optimisation of assembler code for Windows x64 within prologue and epilogue
code is pretty heavily constrained by the calling conventions so some of
your changes between versions don't carry across to Windows.
In particular, unless a frame pointer is declared, the stack pointer must
remain sta
On Tuesday 05 July 2011 17:14:41 Cactus wrote:
> Are you using the AMD code on the Intel Architectures?
>
> Brian
Yep
K8 version on K8,core2,atom,netburst
K10 version on nehalem,sandybridge,bobcat
and I'll tweek the core2 version to use pop/push rather than the redzone , but
that wont affec
Are you using the AMD code on the Intel Architectures?
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mpir-devel/-/MYmAwdish1AJ.
To post to this group, send ema
On Tuesday 05 July 2011 12:23:34 jason wrote:
> On Jul 4, 8:48 pm, Jason wrote:
> > On Monday 04 July 2011 20:21:46 Cactus wrote:
> > > Looks good!
> > >
> > > I notice that there is new k8 assembler. Is this going to be repeated
> > > for the Intel architectures?
> >
> > Yep , the current code
On Jul 4, 8:48 pm, Jason wrote:
> On Monday 04 July 2011 20:21:46 Cactus wrote:
>
> > Looks good!
>
> > I notice that there is new k8 assembler. Is this going to be repeated for
> > the Intel architectures?
>
> Yep , the current code is already an improvement on Intel , but I can do
> better eg t
10 matches
Mail list logo
