Re: [MiNT] [Mint-cvs] [FreeMiNT CVS] freemint/sys/sockets/inet4

[Jo Even Skarstein <joska@online.no>]

Odd Skancke wrote:

>> Anyway, gcc is so slow that it's not practically usable on a plain
>> Falcon. Why are we using this compiler? Because of the lack of
>> alternatives?
> 
>  Well. I think we've got alternatives, but those alternatives is a dead
> end imo. On the other hand, GCC have become too heavy for our hardware
> to manage. So, to me it looks like we're in a "chicken and egg"

I'm no gcc-expert, far from it. But I think that the major reason for
the poor performance (in terms of resource usage) of gcc on our systems
is the build system. make calling make, gcc being loaded for every
single source file... It's not very efficient. I think it should be
possible to gain a lot of speed by building more efficiently.

> situation. For me, the alternatives are no option, as i feel that the
> only chance we have of ever getting FreeMiNT/XaAES to run on other
> hardware is to stick with GCC. I accept the fact that I can never build

Ofcourse, there is always the possibility to adapt ACHH to compile
gcc-oriented sources ;-)

> maintain compatibility. My main developmentenvironment is GCC 4.4.2/KDE
> on Fedora. On this beast, it takes 16 seconds to build the kernel from
> distclean. I dont want to loose that luxury :)

I would probably have to do the same if I want to do any work on
MiNT/XaAES myself. However, I don't feel good about it. I have nothing
against cross-compilers (I'm using avr-gcc on a regular basis and
definitely see the benefits of cross-compiling) but I like to use my
Ataris when doing Atari-related work.

>  One solution could be we branch off the CVS, one for sources that will
> build on the native alternative compilers and one for GCC sources. With

No, I don't like this. I would rather wait for my Milan to finish
compiling or even use my PC.

Jo Even