From patchwork Sun Jan 19 13:02:02 2020
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Gerald Pfeifer
X-Patchwork-Id: 1225443
Return-Path:
X-Original-To: incoming@patchwork.ozlabs.org
Delivered-To: patchwork-incoming@bilbo.ozlabs.org
Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized)
smtp.mailfrom=gcc.gnu.org (client-ip=209.132.180.131;
helo=sourceware.org;
envelope-from=gcc-patches-return-517679-incoming=patchwork.ozlabs.org@gcc.gnu.org;
receiver=)
Authentication-Results: ozlabs.org;
dmarc=none (p=none dis=none) header.from=pfeifer.com
Authentication-Results: ozlabs.org; dkim=pass (1024-bit key;
unprotected) header.d=gcc.gnu.org header.i=@gcc.gnu.org
header.a=rsa-sha1 header.s=default header.b=Jnye57Ck;
dkim-atps=neutral
Received: from sourceware.org (server1.sourceware.org [209.132.180.131])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits)) (No client certificate requested)
by ozlabs.org (Postfix) with ESMTPS id 480w1j2w1nz9sR4
for ;
Mon, 20 Jan 2020 00:02:15 +1100 (AEDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gcc.gnu.org; h=list-id
:list-unsubscribe:list-archive:list-post:list-help:sender:date
:from:to:subject:mime-version:content-type:message-id; q=dns; s=
default; b=OY7v0K3AJEilAG+oZD3Qgq0O3d0HYGhRqptWmPcMsrXb6qPwlfzV+
7k/fEON/TB90AXRF9dcbLvUo5i+QOgzCtfV7rxSBkaCdBrIDaenHDeVXS0e0Vv17
Ioabo+893Qi6DIbaJAz9co/30x0SleFUhQxrTiEaD7HP3SkET4f1L8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gcc.gnu.org; h=list-id
:list-unsubscribe:list-archive:list-post:list-help:sender:date
:from:to:subject:mime-version:content-type:message-id; s=
default; bh=QGhN8VMy7yijf05h4PNDqkl6geo=; b=Jnye57CkRzWmSoeWolYP
yyzPcYpCq+wc+S7vAkDIts33G8vkSzCfXPcf12EUEgiR6bVf88ZRDYw5leBLjhhN
0wr2h4vx9005/c0lR11DBMyRllVUUYepiUkV6NV7whwTJyOmpIr8c466ElOwsufF
71lZBbbDCsM+gluZ8DszopU=
Received: (qmail 37290 invoked by alias); 19 Jan 2020 13:02:08 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id:
List-Unsubscribe:
List-Archive:
List-Post:
List-Help:
Sender: gcc-patches-owner@gcc.gnu.org
Delivered-To: mailing list gcc-patches@gcc.gnu.org
Received: (qmail 37274 invoked by uid 89); 19 Jan 2020 13:02:08 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-21.9 required=5.0 tests=AWL, BAYES_00,
GIT_PATCH_0, GIT_PATCH_1, GIT_PATCH_2, GIT_PATCH_3, KAM_SHORT,
SPF_PASS autolearn=ham version=3.3.1 spammy=obtaining, leaves,
7058, states
X-HELO: hamza.pair.com
Received: from hamza.pair.com (HELO hamza.pair.com) (209.68.5.143) by
sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP;
Sun, 19 Jan 2020 13:02:06 +0000
Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com
(Postfix) with ESMTP id 1B52133E11 for ;
Sun, 19 Jan 2020 08:02:05 -0500 (EST)
Received: from anthias (simmu1-65-185.utaonline.at [62.218.65.185]) (using
TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits)) (No client certificate requested) by hamza.pair.com
(Postfix) with ESMTPSA id B2B0833E10 for ;
Sun, 19 Jan 2020 08:02:04 -0500 (EST)
Date: Sun, 19 Jan 2020 14:02:02 +0100 (CET)
From: Gerald Pfeifer
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Adjustments of "regression hunting" instructions to the
post-SVN world.
MIME-Version: 1.0
Message-Id: <20200119130205.1B52133E11@hamza.pair.com>
X-IsSubscribed: yes
With Git a clone carries the whole repository, so remove instructions
on obtaining a local copy of the repository and related instructions
on SVN usage.
On the way remove a web link for the contrib/reghunt scripts since
those are in the repository anyway.
Pushed.
Gerald
---
htdocs/bugs/reghunt.html | 54 +++-------------------------------------
1 file changed, 4 insertions(+), 50 deletions(-)
diff --git a/htdocs/bugs/reghunt.html b/htdocs/bugs/reghunt.html
index d9c92067..48d7d241 100644
--- a/htdocs/bugs/reghunt.html
+++ b/htdocs/bugs/reghunt.html
@@ -54,9 +54,8 @@ while the range is too large to investigate by hand:
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.
Get GCC sources
-Get a Local Copy of the GCC repository
-
-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 Working Copy
-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.
-
Branch and release dates