This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: New C (and now ObjC) parser, take 4
On Fri, 5 Nov 2004, Paolo Bonzini wrote:
> > This seems reasonable to me if people desire it and with the clear
> > understanding that any changes to parser behavior would need to be made to
> > both parsers at once while both are on mainline
>
> Are there any important parser-related regressions (or open bugs) targeted for
> 4.0?
There are no C parser regressions open. The parser will facilitate fixing
bug 8927 - as a separate followup patch, of course.
Whether it is true as you suggested that this parser affects more code
than the new C++ parser depends on the amounts of C and C++ code out there
compiled by GCC in environments where GCC may get upgraded, but whereas
the C++ parser by design fixed many defects in the old C++ parser and made
it accept a more correct language and be stricter, this parser by design
implements exactly the same language as the old C parser and if it works
properly should have no impact on code that doesn't have syntax errors
with the current parser beyond maybe slightly different diagnostic
location in some cases not covered by the testsuite.
The remaining parser developments before it is ready to replace the old
one should largely be testsuite additions. Tests thoroughly covering
syntax errors might show up a few places where error recovery need
refining, and when bug 18164 is fixed that will facilitate disallowing
wide strings in asm (for which I have patches for both the old and new
parsers, but the testcase gives an ICE which was reduced to the testcase
in that bug) but I don't expect major changes to the parser itself now it
has reached no-regression state.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)