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 Reply-To: Cygwin List Message-Id: <6.0.1.1.0.20031203174050.03531600@127.0.0.1> X-Sender: Date: Wed, 03 Dec 2003 17:42:29 -0500 To: "Krzysztof Duleba" , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: bug in gcc3.3.1 In-Reply-To: References: <120320032215 DOT 12429 DOT bc8 AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Note-from-DJ: This may be spam At 05:41 PM 12/3/2003, Krzysztof Duleba you wrote: >kumarchi wrote: > >> I found conssitent bug in gcc3.3.1 >> >> gcc2xx will compile the fiollwowing with no problem >> >> printf (" ...... >> xxx ", ..) >> >> where the format "...... >> xxx " includes a new line character. >> >> gcc3.3 will nto compile this and looks like it will allow >> an explicit new line inside. > >You can even remove printf and leave only "..... >..... " to get the same compile error. Sorry, can't reproduce it. You're going to have to get allot more specific (i.e. go step-by-step on a simple example you provide) I guess. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/