This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: 3.0 bogus file information in debugging output
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Carlo Wood <carlo at alinoe dot com>
- Cc: gcc-bugs at gcc dot gnu dot org, mark at codesourcery dot com, neil at daikokuya dot demon dot co dot uk
- Date: Wed, 30 Jan 2002 23:26:46 -0800
- Subject: Re: 3.0 bogus file information in debugging output
- References: <20020130205038.GJ754@codesourcery.com> <20020131061926.A7989@alinoe.com>
On Thu, Jan 31, 2002 at 06:19:26AM +0100, Carlo Wood wrote:
> On Wed, Jan 30, 2002 at 12:50:38PM -0800, Zack Weinberg wrote:
> > (There's still a bug with this stuff in 3.1, see next message.)
> >
> > $ cat test.c
> > int main(void) {
> > int i = 0;
> > #line __LINE__ "foo.c"
> > i++;
> > #line __LINE__ "bar.c"
> > return i;
> > }
>
> Perhaps a stupid question, but why doesn't it work in C++?
Dunno. It works in the mainline; perhaps the patches I'm backporting
will fix it in 3.0 (they do their work in c-common.c mostly, so they
may help C++ as well as C).
zw