[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Still don't get it - difference between 68020 and 68020-60
On Mon, 2010-06-21 at 11:00 +0200, Miro Kropacek wrote:
> > You are talking about packages again. I'm not. Increasing the size of
> > the package only happens if the package maintainer wants to produce.
> > He/she can produce a m68000 compiled package and it should work on all
> > Atari's, and completely ignore the other capabilities of GCC.
> Yes, I've mentioned two issues there, first is huge size of gcc
> package (7*2 targets = 112 MB only for libs!) and its compilation
> time, second is our needs. Second thing implies the first one. So if
> we don't need mintlib for more than 3 targets, we don't need gcc for
> more than 3 targets. And *if* someone in the future will need
> something else, we just enable it in gcc (it's matter of few lines,
> everybody can do it, not only Vincent). I really see no point to have
> +112 MB on my Atari + compilation time for one afternoon even on my PC
> :-/
It's a one time build. We're not going to be recompiling GCC every day.
The size of disks these days shouldn't be a problem for 112MB, if it
really is 112MB.
> >
> > And we need -mshort for all targets because the kernel requires -mshort.
> Does it? I thought kernel needs libgcc only in 68000 version because
> of long mul/div emulation.
These are the functions used by -lgcc....
(/usr/lib/gcc/m68k-atari-mint/4.4.3/libgcc.a)_udivsi3.o
(/usr/lib/gcc/m68k-atari-mint/4.4.3/libgcc.a)_divsi3.o
(/usr/lib/gcc/m68k-atari-mint/4.4.3/libgcc.a)_umodsi3.o
(/usr/lib/gcc/m68k-atari-mint/4.4.3/libgcc.a)_modsi3.o
(/usr/lib/gcc/m68k-atari-mint/4.4.3/libgcc.a)_mulsi3.o
(/usr/lib/gcc/m68k-atari-mint/4.4.3/libgcc.a)_divdi3.o
(/usr/lib/gcc/m68k-atari-mint/4.4.3/libgcc.a)_clz.o
Alan.