This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: New C (and now ObjC) parser, take 4


On Thu, 4 Nov 2004, Geoff Keating wrote:

> It's more that static-tree-branch already has several C parser changes on it,
> and more will appear in the future.

I think merging those into the new parser when necessary will be a lot 
easier than merging mainline to static-tree-branch before testing every 
parser change.  Parser behavior and performance are meant to be directly 
comparable to those on mainline - hence arranging it as a drop in 
replacement for the old c-parse.in without changing interfaces to the rest 
of the compiler, hence putting all testcases on mainline first, and where 
possible testcase changes to permit different diagnostics, and hence 
documenting syntax oddities of the old parser and emulating them in the 
new, only fixing them in the new if they are first fixed on mainline.

As and when changes are made to the old parser on mainline, I will fix the 
new parser to emulate the changed behavior.

The proper branch model for the new parser is a branch such that every 
file except for a handful just takes the mainline version, with mainline 
changes as they appear, so only changes to files that might conflict need 
merging from mainline to the branch and changes which make sense on 
mainline go on mainline rather than branching any files unnecessarily.  
But I don't think CVS can approximate this sort of branching of a few 
files.  (And I don't know if it makes sense in the general theory of 
version control systems, it's just the practical work model that seems to 
make sense for this development.)

-- 
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)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]