Re: [user42@zip.com.au: Bug#186789: libgmp3: m68k maybe as m68020]
On Wed, Apr 16, 2003 at 11:49:45AM +1000, Kevin Ryde wrote:
> "Christian T. Steigies" <cts@debian.org> writes:
> >
> > ssh2 and libssl and whatever is needed for that would benefit _a lot_ from
> > some 060 improvements. ssh2 is basically unusable on 060 boxes, it takes
> > minutes to connect... didn't one of the Richard's play with that some time
> > ago?
>
> I forget who it was, it might have been about sparc though, where the
> v8 code was/is a lot faster than the default v7.
v7, v8? Thats for ssh2?
> Incidentally, if anyone wants to write some good, fast, well-tested
> asm code for gmp on 68060 it'd be gratefully received. It's a bit
> hard to get too excited about old chips that are always going to be
> quite slow, but if someone's got one and wants to improve things for
> it then there's every chance some simple stuff could be an
> improvement.
I don't think many people still write asm, especially not for 68060...
But I heard the gcc compiler produced pretty good code, if you just give it
the right options.
> I guess as a minimum the gmp configs ought to select the 68000 code in
> preference to the 68020 when building for 060.
I didn't follow this too closely, but I think the reasoning was you use
-m68020-060 to build code that is "optimized" for all chips, ie uses no
instructions that need to be emulated. The drawback is, that it slows down
020-040 quite a bit. That's why Richard suggested one deb optimized for
020-040, which runs pretty fast on all those chips, and one for 060, which
should be way faster than the one-for-all version. But I'd prefer if
somebody who knows about this, ie Richard, explains it again. AFAIK this has
never been done on m68k yet.
Christian
Reply to: