X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <21121381 DOT 1187609140532 DOT JavaMail DOT root AT elwamui-cypress DOT atl DOT sa DOT earthlink DOT net> <46C97DA9 DOT D743EE5F AT dessent DOT net> Subject: RE: Line info causes GCC to bomb? Date: Mon, 20 Aug 2007 16:22:58 +0100 Message-ID: <07c001c7e33d$fd394e90$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <46C97DA9.D743EE5F@dessent.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 20 August 2007 12:40, Brian Dessent wrote: > g6522c wrote: > >> If I can locate the relevant routines in gcc I might be able to provide a >> patch. My > > I wouldn't spend too much effort on that. It's fixed in 4.x, and the > 3.x branches were closed a long time ago. OTOH, it might be nice to > have this fixed in the Cygwin-distributed gcc; however since it seems to > be a rather esoteric corner case it's not a huge priority. It's not that likely that I'll spin any more cygwin 3.x releases, unless there's huge demand for it or some bug crops up that impacts a lot of people in everyday use, but please do Cc me if you generate any patch, because it might just happen. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/