From mint-bounce@lists.fishpool.fi Wed Dec 9 11:40:07 2009 Message-ID: <4B1FD27D.1010600@atari-source.org> Date: Wed, 09 Dec 2009 11:38:21 -0500 From: Mark Duckworth User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Jo Even Skarstein CC: mint@lists.fishpool.fi Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3 References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <1260278588.20336.221.camel@jetpack.demon.co.uk> <4B1E5596.9010300@freesbee.fr> <200912082209.08699.oak@helsinkinet.fi> <4B1FAB84.1000009@atari-source.org> <4B1FB1D4.70704@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mduckworth@atari-source.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Jo Even Skarstein wrote: > ------------------------------------------------- > From: "Vincent Rivière" > Sent: Wednesday, December 09, 2009 3:19 PM > To: > Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3 > >> I don't want to say here that GCC is bad software. >> Like any software, it has bugs. And 99.5% of the time, it works very >> well. It has not more bugs than other software of the same size, it has > > The biggest problem with gcc is not bugs. As you say, it actually > works very well. The real problem is that it's very, very, very, very > slow. Even on my Milan060 it's too slow to be used for actual > development. Sometimes I wish that MiNT/XaAES could be compiled with > PureC again. Then I could even look for and possibly fix bugs myself. > Now I'm just too impatient to wait for gcc to finish. I was poking > around XaAES about a year ago, doing some minor modifications just to > get familiar with the code. I gave up. I make too many errors while > typing, and spent too much time waiting for gcc to tell me that > something is wrong, but it can't tell me where. It's easier with Pure > C. Alt+C, and in a second I get a long, nice list of my errors, with > (correct!) line-numbers and all. I think the answer to this is distcc. Use a hosted gcc cross compiler on a fast linux box and set gcc to do all the work on that, putting the results back to your milan. I don't know if it will work and I haven't had a lot of time lately, but this is how I intend to improve performance of my aranym build farm. Thanks, Mark