Re: Technique for finding regressions in the C++ parser

[Phil Edwards <phil at jaj dot com>]

On Fri, Nov 29, 2002 at 09:34:16PM -0500, Craig Rodrigues wrote:
> (2)  Check out gcc from the read-only CVS repository with the CVSROOT
>      :pserver:anoncvs@subversions.gnu.org:/cvsroot/gcc
>      (be kind to developers who use the read/write repository)
>      according to the instructions at http://gcc.gnu.org/cvs.html
[...]
> You can repeat steps (2)-(4), but use the cvs co -D [DATE] to check out
> a version of GCC from a different date.

If you plan on doing a lot of cvs commands, I recommend grabbing a subset
of the repository itself.  Then do the checkout locally.  Subsequent CVS
commands run with no waiting -- even kinder to the developers using the
read/write repo.

Instructions at

    http://gcc.gnu.org/rsync.html

The first download is a PITA for slow connections.  (The 450MB mentioned
on that page is outdated -- now that the freakin' gigantic Ada stuff is
in the repo, it's about a gig, but you can pass --exclude='gcc/gcc/ada/'
(note the trailing slash, and you'll need to exclude other directories too)
to the rsync command.)


> You can then do:
> cvs diff -D [DATE1] -D [DATE2] [file] 
> to find out what changes occured on a file or directory.

"cvs log -N" and "cvs annotate" are also very handy here.


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002