From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: C++ Parser Merge
Date: Fri, 27 Dec 2002 12:24:00 -0000 [thread overview]
Message-ID: <200212271904.gBRJ4NL01383@localhost.localdomain> (raw)
I'm recovering from the Norwalk Virus (don't worry -- you can't catch
it by email), but I think I'm capable of doing the merge.
There are three major components:
(1) V3 changes
These are for random invalid bits in V3 that the old parser didn't
catch, but the new one does. Nothing controversial, I don't
think.
(2) Testsuite changes
The parser changes necessitate changes to the testsuite; some new
errors, some changed messages, etc.
Most of these are non-controversial; I'll call out any that I
think people might have something to say.
(3) The front end code itself.
I intend to do the merge in the order above.
There will undoubtedly be fall-out, but I don't think it will be too
great -- we've run a fair amount of real code, beyond what is in our
testsuites, through the parser, with good results.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next reply other threads:[~2002-12-27 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 12:24 Mark Mitchell [this message]
2002-12-27 12:54 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 23:30 Mark Mitchell
2002-12-24 2:03 ` Gabriel Dos Reis
2002-12-24 2:19 ` Mark Mitchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212271904.gBRJ4NL01383@localhost.localdomain \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).