Line info causes GCC to bomb?

[Brian Dessent]

g6522c@earthlink.net 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.

Brian

--
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/