From mint-bounce@lists.fishpool.fi  Tue Jan 22 17:29:30 2008
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Subject: Re: [MiNT] GCC 4.2.2 and binary compatibility
From: Alan Hourihane <alanh@fairlite.demon.co.uk>
To: Vincent =?ISO-8859-1?Q?Rivi=E8re?= <vincent.riviere@freesbee.fr>
Cc: mint@fishpool.com
In-Reply-To: <475850B5.4040802@freesbee.fr>
References: <4747F03E.4050101@freesbee.fr>  <4752B129.4010106@freesbee.fr>
	 <1196949946.9217.29.camel@localhost>  <47583601.7070107@freesbee.fr>
	 <1196968336.9217.60.camel@localhost>  <475850B5.4040802@freesbee.fr>
Content-Type: text/plain; charset=UTF-8
Date: Thu, 06 Dec 2007 22:42:14 +0000
Message-Id: <1196980934.9217.83.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.1 
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: alanh@fairlite.demon.co.uk
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00
X-Spam-Level: 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by freemint id m0MGP1b9004618
Status: 
X-Status: 
X-Keywords:                   

On Thu, 2007-12-06 at 20:42 +0100, Vincent Rivière wrote:
> >> However, GCC 4.2.2 is now quite stable.
> > 
> > For me too. I've just compiled FreeMiNT CVS with it (with some patching)
> > and I'm running with that version right now :-)
> 
> I'm VERY happy to know this :-) ! What a success story !
> You should submit your patches to the FreeMiNT developers. Most of the 
> times, GCC 4 is more strict than earlier versions, and may be useful to 
> find potentially dangerous code.

Yes, I'm definitely going to submit them here.

Frank - given that you are the maintainer of FreeMiNT - what's your
position on leaving gcc 2.95.3 finally behind and upgrading to GCC 4.2.2
for FreeMiNT kernel builds ?

Alan.