This is the mail archive of the
mailing list for the Cygwin project.
[firstname.lastname@example.org: Re: [MinGW-dvlpr] GCC 4.3.0 i386-pc-mingw32 ALPHA Release]
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 6 Apr 2008 23:45:05 -0400
- Subject: [angray: Re: [MinGW-dvlpr] GCC 4.3.0 i386-pc-mingw32 ALPHA Release]
- Reply-to: cygwin-apps at cygwin dot com
Are the changes here usable for cygwin?
----- Forwarded message from Aaron Gray -----
From: Aaron Gray
To: MinGW Devlopers Discussion List
Subject: Re: [MinGW-dvlpr] GCC 4.3.0 i386-pc-mingw32 ALPHA Release
Date: Fri, 4 Apr 2008 15:39:08 +0100
A few dumb question here.
> I've uploaded a binary release of GCC 4.3.0 to the FRS.
Whats the FRS ?
> You can get it in the usual place in the FRS as either
> gcc-4.3.0-mingw-alpha-20080403.7z or
> This release is intended for testing GCC, and not for general
> development use.
> Warning: This is an alpha release. That means the build contains
> serious problems that are likely to cause serious problems, including
> silent incorrect code compilation.
Okay, will test.
> Extract it somewhere. Add the bin/ folder to your PATH variable.
> If you extract this over your existing MinGW installation, it will
> replace your current GCC version's driver executables and documentation.
> This release uses about 500 megabytes of disk space when decompressed.
> This is a GCC 4.3.0 tree, with the following changes
> shared libgcc enabled
> vtable symbol fix
> main symbol fix
> static object build system fix
> These are mainly derived from Danny's 4.2 patchset.
Are these patches availiable some where, or are they from 4.2 diff's ?
> All languages (Ada, C, C++, Fortran, Java, Objective-C, Objective-C++)
> appear to be basically working. The testsuite results are fairly bad,
> so they may not be working very well.
> Two major components are disabled : OpenMP support and mudflap pointer
> This release is probably ABI incompatible with all other GCC versions
> for all languages other than C. C should be OK for portable code that
> isn't compiled with exception support.
> This release is compiled to support Dwarf2 exception handling only.
> Dwarf2 is mutually incompatible with all other exception handling
> schemes, and foreign frames.
> If you want to throw exceptions between modules, you need to compile
> with -shared-gcclib.
Is this compiled on Cygwin or with MinGW ?
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
MinGW-dvlpr mailing list
----- End forwarded message -----