From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
The first three steps are described below. They can be automated,
-as can the framework for the binary search. The directory
-contrib/reghunt
in the GCC repository includes
+as can the framework for the binary search. The directory
+contrib/reghunt
in the GCC repository includes
scripts to do this work.
There are several short cuts @@ -70,58 +69,13 @@ are simple to work around.
Using rsync to get a local copy of the GCC -repository is highly recommended for regression hunts. You'll -be checking out the tree used for the regression search over and over -again and won't want to affect access times for other GCC developers -who are using the real repository, and it will also be faster for -you.
- -The full tree takes a lot of disk space, but it's possible to -exclude directories you won't need for your hunt. If you're already -using a local SVN repository via rsync, -you can make a cut-down version of it that leaves out directories you -don't need for the regression hunt. This makes SVN operations much -quicker, making it worthwhile even if the copy is on the same system. -It's particularly useful if you'll want to copy it to a system that is -low on available disk space. The following, for example, makes a -smaller copy of the repository that can be used for finding C and C++ -compile-time problems and takes only half the disk space as the full -repository.
- -- cat <<EOF > rsync_exclude - --exclude=gcc-svn/benchmarks - --exclude=gcc-svn/boehm-gcc - --exclude=gcc-svn/old-gcc - --exclude=gcc-svn/wwwdocs - --exclude=gcc-svn/gcc/libstdc++-v3 - --exclude=gcc-svn/gcc/gcc/ada - --exclude=gcc-svn/gcc/gcc/testsuite - EOF - - tar `cat rsync_exclude` -cf - gcc-svn | gzip > gcc-svn.tar.gz -- -
Check out a local working copy of -GCC from your local repository. If you are not using a local -repository, then check out a working copy using anonymous read-only SVN access. In any case, -use a new working copy that is separate from what you use for +
Check out a working copy using Git. +Use a new working copy that is separate from what you use for development or other testing, since it is easy to end up with files in strange states.
-Information about checking out specific dates, working with branches and tags, and -inspecting the commit logs is available at the SVN Help pages in the GCC -Wiki.
-