Parser bug?

Mumit Khan khan@xraylith.wisc.EDU
Tue Aug 31 22:45:00 GMT 1999


Jeffrey A Law <law@cygnus.com> writes:
>   In message <199907051612.LAA22805@mercury.xraylith.wisc.edu>you write:
>   > The parser bug K. Haley is referring to is a really tricky one that
>   > either crashes the compiler on some platforms (x86-win32) or gets
>   > bizarre parse errors on some others (ix86-pc-linux-gnu).
>   > 
>   > Here's a much simplified example (KH's was a monster testcase that I
>   > ``accidentally'' figured out why it was making the compiler get parse
>   > errors for no reason):
> I believe this patch from Jim (which I have brought into the gcc-2.95 release
> branch for the gcc-2.95.1 release fixes the problem):
> 
>         Thu Jul 15 15:40:09 1999  Jim Wilson  <wilson@cygnus.com>
>         * tree.c (build_type_attribute_variant): Move current_obstack restore
>         after build_qualified_type call.
> 

It certainly does, and I've been using it since the day Jim added it. It's
also one of the essential "extras" that's part of my binary release.

Thanks for adding it to the release branch.

Regards,
Mumit



More information about the Gcc-bugs mailing list