Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <6.1.2.0.0.20041116182733.02188880@imap.myrealbox.com> X-Sender: tprince AT imap DOT myrealbox DOT com Date: Tue, 16 Nov 2004 18:32:11 -0800 To: Mikael =?iso-8859-1?Q?=C5sberg?= , From: Tim Prince Subject: Re: g++ 3.4.1 In-Reply-To: <00c701c4cc08$990fa300$0200a8c0@mindcooler> References: <00c701c4cc08$990fa300$0200a8c0 AT mindcooler> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed X-IsSubscribed: yes Note-from-DJ: This may be spam Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id iAH2WOIK027454 At 10:17 AM 11/16/2004, Mikael Åsberg wrote: >"Martin Magnusson" wrote: >>I just tried upgrading from g++ 3.3.1 (which currently gives me an >>"internal compiler error" on my code) to the 3.4.1 version available from >>the Cygwin setup. After doing so, however, I get a flood of error messages >>about the many templates I have (such as "template-id xxx for yyy does not >>match any template declaration" and several other). >> >>Should I start to adapt my code to gcc 3.4.1, or would it be safer to wait >>until it is available as default from the setup? Is it likely that the >>error messages I get is due to the Cygwin port, or would it be g++ itself? >> >>/ martin > >g++ version 3.4.x is alot less forgiving (read: more compliant) than >earlier versions of g++ (GCC) were regarding standard C++. This is a good >thing. >I haven't used the test version you mention but I've been compiling my >own versions of GCC under Cygwin for some time and right now >I am using the latest version (3.4.3). I haven't had any problems other >than not being able to use -mno-cygwin anymore but I can live with that. >So, you probably have problems with your C++ code, i.e. it's not standard- >compliant but GCC used to accept it. Crank up the warning levels and turn >off compiler extensions and start fixing the code. ICE is probably the fault of the compiler, regardless of any possible shortcomings of your source code. Other than that, I have no disagreement with Mikael. If you "fix the code" and still provoke problems, there is some advantage in submitting bug reports against a version which is currently actively maintained. Tim Prince -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/