[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [user42@zip.com.au: Bug#186789: libgmp3: m68k maybe as m68020]



On Sat, Apr 05, 2003 at 01:49:55AM -0500, Steve M. Robbins wrote:
> Hello,
> 
> I'm the maintainer of gmp, but fairly ignorant of debian/m68k.
> Would anyone here care to comment? 
> 
> Thanks,
> -Steve
> 
> ----- Forwarded message from Kevin Ryde <user42@zip.com.au> -----
> 
> Date: Sun, 30 Mar 2003 07:46:00 +1000
> From: Kevin Ryde <user42@zip.com.au>
> Subject: Bug#186789: libgmp3: m68k maybe as m68020
> To: submit@bugs.debian.org
> Reply-to: Kevin Ryde <user42@zip.com.au>, 186789@bugs.debian.org
> X-Debian-PR-Message: report 186789
> X-Debian-PR-Package: libgmp3
> X-Debian-PR-Keywords:
> Original-recipient: rfc822;steven.robbins@videotron.ca
> 
> Package: libgmp3
> Version: 4.1.2-1
> Severity: wishlist
> 
> Is it true that debian m68k means 68020 or higher?  Without having an
> actual debian m68k to look at, from nosing around some m68k packages I
> take it gcc defaults to 68020 and generates code that won't actually
> run on an 000 or 010.

correct. Linux kernel won´t support anything <020

> If this is so then it'd be an advantage to build gmp as m68020
> similarly.  gmp nowadays takes cpu type "m68k" to mean plain 68000,
> compiling for "m68020" should result in code that's faster, and
> probably a little smaller.

it would run faster on 68020-40 CPU´s, the problem is it would
also run *much* slower on 68060 CPU´s.. so there should be 
2 version of it built.

Richard



Reply to: