3.0 bogus file information in debugging output

Zack Weinberg zack@codesourcery.com
Wed Jan 30 13:57:00 GMT 2002


On Wed, Jan 30, 2002 at 12:56:40PM -0800, Mark Mitchell wrote:
> Zack Weinberg <zack@codesourcery.com> wrote:
> 
> >3.0.3 seems to have the same bug with functions with #line in the
> >middle, that Neil fixed for the mainline not so long ago.  I think
> >this is worth addressing in 3.0.4.
> >
> >(There's still a bug with this stuff in 3.1, see next message.)
> 
> Assuming this is a regression from GCC 2.95, 

It is.

> and assuming that you
> think Neil's patch is not likely to introduce new problems,

My bad - it's not Neil who fixed it in 3.1, it was Jason Merrill.

There are two patches that might be worth considering for 3.0:

http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01082.html
	(Jason's patch to deal with a change of filename in the middle
	of a function)

http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00278.html
	(Jeff Law's patch to get line numbers correct in multi-line
	conditionals)

And then, having seen what they both did, I think I know what's wrong
with the filename info for the beginning of a function, and will try
to patch it for 3.1 - then we might want to consider *that* for 3.0.

zw



More information about the Gcc-bugs mailing list