From patchwork Fri Jun 27 11:26:29 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gerald Pfeifer X-Patchwork-Id: 364879 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org 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 214C11400DD for ; Fri, 27 Jun 2014 21:26:44 +1000 (EST) 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:cc:subject:message-id:mime-version:content-type; q=dns; s=default; b=yn8esG8hN8fzdIgdkDqUyurpWUQ9qQm/mfFQSod9MH/Z8dDSt9 JqbuV17LNRBch1/xzZihNyRvvnb2N9Ora8Km7xrKbtXaLS1wLVwo9UCfDhZytbNK XIW6RjmcSjqN4nLTdCWnq/jRq0U5w3hWEn82yvcfsKwNq8y/PkXDdVZRE= 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:cc:subject:message-id:mime-version:content-type; s= default; bh=whBl7EN/iBwbKZWb7Buf+vEyvSA=; b=iXoOhCnkHJX/UCa+Zg/5 KvtiFIk4sEzX71QZWy3wTG/aWt7PLsMSXLBwgkQNaxNEq0Psb4XWASS8pFq8FXWn w5CoxvpumjX8jXqOhrchon3rl/DjUrCLEMNPplVS035+aZY3MxTrMkmMJ3PMDb5r VzTShD4m40/PubSvy90kMRU= Received: (qmail 8391 invoked by alias); 27 Jun 2014 11:26:38 -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 8380 invoked by uid 89); 27 Jun 2014 11:26:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL, BAYES_00, SPF_PASS autolearn=ham version=3.3.2 X-HELO: ainaz.pair.com Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 27 Jun 2014 11:26:36 +0000 Received: from [192.168.0.131] (vie-188-118-252-235.dsl.sil.at [188.118.252.235]) by ainaz.pair.com (Postfix) with ESMTPSA id 574893F41D; Fri, 27 Jun 2014 07:26:33 -0400 (EDT) Date: Fri, 27 Jun 2014 13:26:29 +0200 (CEST) From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org cc: Tobias Burnus Subject: [wwwdocs] Shorten contribute.html a bit and convert links to https Message-ID: MIME-Version: 1.0 X-IsSubscribed: yes Applied. (gcc-bugs also has changed its usage, it's not meant for direct posting any more.) Gerald Index: contribute.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v retrieving revision 1.84 diff -u -r1.84 contribute.html --- contribute.html 22 Jun 2014 13:07:07 -0000 1.84 +++ contribute.html 27 Jun 2014 11:07:43 -0000 @@ -68,10 +68,9 @@

Submissions which do not conform to the standards will be returned with a request to address any such problems. To help with the -preparation of patches respecting these rules, one can use the script - -contrib/check_GNU_style.sh to detect some of the common -mistakes.

+preparation of patches you can use the script +contrib/check_GNU_style.sh.

Testing Patches

@@ -79,8 +78,7 @@

All patches must be thoroughly tested. We encourage you to test changes with as many host and target combinations as is practical. In addition to using real hardware, you can -use simulators to increase your test -coverage.

+use simulators.

Much of GCC's code is used only by some targets, or used in quite different ways by different targets. When choosing targets to test a @@ -91,7 +89,7 @@

You will of course have tested that your change does what you expected it to do: fix a bug, improve an optimization, add a new -feature. If the test framework permits, you should automate these +feature. Where possible you should automate these tests and add them to GCC's testsuite. You must also perform regression tests to ensure that your patch does not break anything else. Typically, this means comparing post-patch test results to @@ -104,9 +102,8 @@

If your change is to code that is not in a front end, or is to the C front end, you must perform a complete build of GCC and the runtime libraries included with it, on at least one target. You must -bootstrap all default languages, not just C. You must also run all of the -testsuites included with GCC and its runtime libraries. For a normal -native configuration, running

+bootstrap all default languages, not just C, and run all testsuites. +For a normal native configuration, running

 make bootstrap
 make -k check
@@ -141,9 +138,7 @@
 
In all cases you must test exactly the change that you intend to
 submit; it's not good enough to test an earlier variant.  The tree
 where you perform this test should not have any other changes applied
-to it, because otherwise you cannot be sure that your patch will work
-correctly on its own.  Include all your new testcases in your
-testsuite run.

+to it.  Include all your new testcases in your testsuite run.

 
 
 
Documentation Changes

@@ -192,8 +187,7 @@
 For new features a description of the feature and your implementation.
 For bugs a description of what was wrong with the existing code, and a
 reference to any previous bug report (in the
-GCC bug tracker or the
-gcc-bugs archives) and any
+GCC bug tracker) and any
 existing testcases for the problem in the GCC testsuite.