From: Paul Brook <paul@codesourcery.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Move VFP11 scheduler description
Date: Fri, 29 Aug 2008 15:13:00 -0000 [thread overview]
Message-ID: <200808281717.14261.paul@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0808271954060.23732@digraph.polyomino.org.uk>
On Wednesday 27 August 2008, Joseph S. Myers wrote:
> On Tue, 26 Aug 2008, Paul Brook wrote:
> > The attached patch moves the VFP11 scheduler description into its own
> > file. No functional changes, just an aesthetic cleanup to separate
> > generic VFP code from the cpu specific scheduler.
>
> You've put the old GPLv2 license notice in vfp11.md. It should have the
> current GPLv3 license notice (without an FSF address).
I thought I'd fixed this before committing the patch, but apparently not. I've
applied the following patch which copies the license notice from arm.md.
Paul
2008-08-28 Paul Brook <paul@codesourcery.com>
* config/arm/vfp11.md: Update license notice.
* config/arm/cortex-r4.md: Ditto.
Index: gcc/config/arm/cortex-r4.md
===================================================================
--- gcc/config/arm/cortex-r4.md (revision 139716)
+++ gcc/config/arm/cortex-r4.md (working copy)
@@ -4,15 +4,19 @@
;; This file is part of GCC.
+;; GCC is free software; you can redistribute it and/or modify it
+;; under the terms of the GNU General Public License as published
+;; by the Free Software Foundation; either version 3, or (at your
+;; option) any later version.
+
;; GCC is distributed in the hope that it will be useful, but WITHOUT
;; ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
;; or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public
;; License for more details.
;; You should have received a copy of the GNU General Public License
-;; along with GCC; see the file COPYING. If not, write to
-;; the Free Software Foundation, 51 Franklin Street, Fifth Floor,
-;; Boston, MA 02110-1301, USA.
+;; along with GCC; see the file COPYING3. If not see
+;; <http://www.gnu.org/licenses/>.
(define_automaton "cortex_r4")
Index: gcc/config/arm/vfp11.md
===================================================================
--- gcc/config/arm/vfp11.md (revision 139716)
+++ gcc/config/arm/vfp11.md (working copy)
@@ -3,21 +3,20 @@
;; Written by CodeSourcery.
;;
;; This file is part of GCC.
-;;
+
;; GCC is free software; you can redistribute it and/or modify it
-;; under the terms of the GNU General Public License as published by
-;; the Free Software Foundation; either version 2, or (at your option)
-;; any later version.
-;;
-;; GCC is distributed in the hope that it will be useful, but
-;; WITHOUT ANY WARRANTY; without even the implied warranty of
-;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-;; General Public License for more details.
-;;
+;; under the terms of the GNU General Public License as published
+;; by the Free Software Foundation; either version 3, or (at your
+;; option) any later version.
+
+;; GCC is distributed in the hope that it will be useful, but WITHOUT
+;; ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
+;; or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public
+;; License for more details.
+
;; You should have received a copy of the GNU General Public License
-;; along with GCC; see the file COPYING. If not, write to the Free
-;; Software Foundation, 51 Franklin Street, Fifth Floor, Boston, MA
-;; 02110-1301, USA. */
+;; along with GCC; see the file COPYING3. If not see
+;; <http://www.gnu.org/licenses/>.
(define_automaton "vfp11")
prev parent reply other threads:[~2008-08-28 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 18:50 Paul Brook
2008-08-28 19:43 ` Joseph S. Myers
2008-08-29 15:13 ` Paul Brook [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808281717.14261.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).