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

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



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.

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.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux blah 2.2.15 #1 Tue Apr 25 17:13:48 EST 2000 i586
Locale: LANG=C, LC_CTYPE=C

Versions of packages libgmp3 depends on:
ii  libc6                         2.3.1-15   GNU C Library: Shared libraries an

-- no debconf information


----- End forwarded message -----



Reply to: