Message-ID: <005a01c316e7$8d7a6110$0100a8c0@acp42g>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Cc: <djgpp-workers AT delorie DOT com>
References: <200305071759 DOT h47HxQte028947 AT speedy DOT ludd DOT luth DOT se> <200305072355 DOT 16047 DOT pavenis AT latnet DOT lv> <200305072055 DOT h47KtG6q010180 AT envy DOT delorie DOT com> <200305080936 DOT 52719 DOT pavenis AT latnet DOT lv> <010101c31617$29c4fb60$0100a8c0 AT acp42g> <3405-Sat10May2003114559+0300-eliz AT elta DOT co DOT il>
Subject: Re: (fwd) Re: SIGILL 386 (illegal opcode)
Date: Sat, 10 May 2003 21:30:24 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Reply-To: djgpp-workers AT delorie DOT com

> > For the next alpha release do you think we should switch to GCC 3.2.3 or
> > move to 3.3 snapshots with the assumption that GCC 3.3 is realeased
before
> > the 2.04 is released?
>
> My $0.02 worth: I'm generally opposed to building production software
> with compiler and binutils that were released only recently, to say
> nothing of development snapshots.  The risk of being hit by an unknown
> bug is too high, and we cannot afford frequent releases to fix such
> problems when they are become known.
>
> Does GCC 3.2.3 have some grave bug that we wish to avoid?  If so, why
> not use 3.1.x or even 2.95.x?  What do we lose?

The 3.0 and 3.1 have quite a few nasty bugs that have been fixed in the next
release(s) so I would avoid them. I have not looked at the GCC 3.3 changes,
but there are allot and most won't affect us. The GCC 3.2 series is stable.
The 3.x series is allot more compliant than the 2.95.3 with the latest C++
standard and from the 3.3 pages it looks like it may be more stable than the
3.2 serie as it looks like it is going through more testing than the
previous versions.

The C++ ABI as been broken on a number of GCC releases and as such the
2.95.x and the GCC 3.x is not compatible and even within the GCC 3.x series
there are incompatabilities. I do not know what GCC 3.x.y is ABI compatible
with 3.a.b. Remember this has occured numerouse times in the past with major
GCC versions such as 2.6->2.7, 2.7->2.8, 2.8->2.9, 2.9->3.0 and some of the
3.x updates. This is based on reading the GCC 3.x release notesd and chanegs
log and info at the GCC home page.

Regards,
Andrew