Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
x-gfisavedcharset:	Windows-1252
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID:	<C9150052B112D3119E9E0004ACA6E4370345C9A8@tepg1.tepg.co.uk>
From:	"Bruce Adams [TEPG Sunbury]" <bruadams AT tycoint DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	Why is gcc 3.2 prerelease?
Date:	Wed, 5 Mar 2003 10:24:55 -0000
MIME-Version:	1.0
X-OriginalArrivalTime:	05 Mar 2003 10:26:13.0078 (UTC) FILETIME=[A57E3760:01C2E301]

Hi,
   The answer to this question ought to be in the documentation somewhere
but I couldn't find it.
The version of gcc installed by setup is:

  gcc version 3.2 20020818 (prerelease)

Ignoring the 2.9x version.  Why are we still using a prerelease version?  
According to gcc.gnu.org the versions available are:

GCC 3.2.2 
February 5, 2003

GCC 3.2.1 
November 19, 2002

GCC 3.2              - first official release - dated earlier than our
"prerelease".
August 14, 2002 


  Are there special requirements for a cygwin release or is it simply a
question of manpower?
The reason I ask is that I need to use gcc 3.0 for its better ISO C++
compliance and STL but
I'm having a lot of problems with programs compiling (and linting) perfectly
but crashing when
run.  
  I'm not very conversant with 80x86 assembly but when I put these in gdb it
shows the
illegal operation as occurring either before main is entered (as in the
example I posted a
couple of days ago) or at the tail end of a destructor on exit (after the
close brace just to 
make things worse).  
  Its one thing when my code fails because I've made a mistake 
but when it fails because the compiler isn't working I get worried.  
  Another thing that worries me is that gdb shows "(bad)" for some assembly
instructions.  
I am hoping this is a deficiency of gdb rather than gcc but some reassurance
would be nice.
			Regards,
				  Bruce A.




============================================================================
 Any opinions expressed in this e-mail are those of the individual and not
 necessarily those of Tyco Safety Products.

 Any prices for the supply of goods or services are only valid if supported
 by a formal written quotation.

 This e-mail and any files transmitted with it, including replies and
 forwarded copies (which may contain alterations) subsequently transmitted
 from Tyco Saftey Products are confidential and solely for the use
 of the intended recipient.

 If you are not the intended recipient or the person responsible for
 delivery to the intended recipient, be advised that you have received this
 e-mail in error and that any use is strictly prohibited.  In this event,
 please notify us via e-mail at 'helpdesk DOT tepg AT tycoint DOT com' or telephone on 
 0121 255 6499 and then delete the e-mail and any copies of it.
============================================================================






--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -