This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[wwwdocs] svnwrite.html PATCH for Re: [PATCH] Fix hoist-register-pressure testcases for -m31 on s390x
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Mike Stump <mikestump at comcast dot net>
- Cc: Jeff Law <law at redhat dot com>, Andreas Krebbel <krebbel at linux dot vnet dot ibm dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 6 Apr 2015 14:15:21 +0200 (CEST)
- Subject: [wwwdocs] svnwrite.html PATCH for Re: [PATCH] Fix hoist-register-pressure testcases for -m31 on s390x
- Authentication-results: sourceware.org; auth=none
- References: <20150219172754 dot GC9261 at maggie> <54E782C1 dot 9050007 at redhat dot com> <4FB1CEFB-F9C9-4795-917A-EB2218363072 at comcast dot net>
On Fri, 20 Feb 2015, Mike Stump wrote:
>> Yes. ISTM that this kind of patch (twiddling target conditionals in
>> the testsuite) should be OK for a target maintainer to apply without
>> requesting approval, even though it's not in the backend proper.
> Yes, that’s right.
I tried to capture this in our documentation now and applied the
patch below. Let me know if you'd like to see this tweaked.
Gerald
Index: svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.33
diff -u -r1.33 svnwrite.html
--- svnwrite.html 14 Jul 2014 09:45:48 -0000 1.33
+++ svnwrite.html 6 Apr 2015 12:13:12 -0000
@@ -107,9 +107,10 @@
<dd><p>This is for people who have primary responsibility for ports,
front ends, or other specific aspects of the compiler. These folks
are allowed to make changes to areas they maintain and related
- documentation, web pages, and test cases without approval from
- anyone else, and approve other people's changes in those areas. They
- must get approval for changes elsewhere in the compiler.</p>
+ documentation, web pages, and test cases (and target conditionals)
+ without approval from anyone else, and approve other people's changes
+ in those areas.
+ They must get approval for changes elsewhere in the compiler.</p>
<p>Maintainers of a port maintain the relevant files in
<code>gcc/config</code>, documentation, web pages, and test cases