From mint-bounce@lists.fishpool.fi  Tue Jan 22 17:29:31 2008
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
To: <mint@fishpool.com>
From: Peter Slegg <p.slegg@scubadivers.co.uk>
Subject: Re: [MiNT] GCC 4.2.2 and binary compatibility
Reply-To: Peter Slegg <p.slegg@scubadivers.co.uk>
X-Mailer: MyMAIL Rev:1.88.12854 (Atari/(STiK/STinG/GlueSTiK))
X-Hardware: Atari Milan
Content-Type: text/plain;
Date: Thu, 6 Dec 2007 23:20:32 +0200 (GMT)
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <002611af.01bb4ae84840@smtp.freeola.net>
References: <475850B5.4040802@freesbee.fr>
In-Reply-To: 475850B5.4040802@freesbee.fr
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: p.slegg@scubadivers.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=3.3 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00, HEADER_COUNT_CTYPE, MISSING_MIMEOLE, MISSING_OUTLOOK_NAME
X-Spam-Level: ***
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by freemint id m0MGP1bA004618
Status: 
X-Status: 
X-Keywords:                   

On Thu, 06 Dec 2007 20:42:45 , Vincent Riviÿre <vincent.riviere@freesbee.fr> 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.
>
> Someone reported that EmuTOS was successfully compilable (and usable !)
> with GCC 4.2.2.
>
> Really, the next step is to update the MiNTLib !
>
> Vincent
>


I don't know quite how important this is but I know people have been
trying to get GCC 4 working for years.

Presumably some things that won't compile under the old GCC can now
be built ?

Well done.

Peter