obtained gcc-4.6.4.tar.bz2 from upstream website;upstream

verified gcc-4.6.4.tar.bz2.sig;
imported gcc-4.6.4 source tree from verified upstream tarball.

downloading a git-generated archive based on the 'upstream' tag
should provide you with a source tree that is binary identical
to the one extracted from the above tarball.

if you have obtained the source via the command 'git clone',
however, do note that line-endings of files in your working
directory might differ from line-endings of the respective
files in the upstream repository.

1 files changed, 16 insertions, 0 deletions

diff --git a/contrib/reghunt/date_based/README b/contrib/reghunt/date_based/README
new file mode 100644
index 000000000..c674ffc6c
--- /dev/null
+++ b/contrib/reghunt/date_based/README
@@ -0,0 +1,16 @@
+This directory contains scripts that are used for identifying the
+patch that introduced a regression.  General information about such
+searches is covered in http://gcc.gnu.org/bugs/reghunt.html.
+
+  reg_search searches for a small time interval within a range of
+  dates in which results for a test changed, using a binary search.
+  The functionality for getting sources, building the component to
+  test, and running the test are in other scripts that are run from
+  here.
+
+  reg_periodic invokes separate tools (the same scripts invoked by
+  reg_search) over a range of dates at specified intervals.
+
+  reg_test_template shows the format for the script that runs a test
+  and determines whether to continue the search with a later or
+  earlier date.