From: Richard Sandiford <richard.sandiford@arm.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jeffrey Law <law@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
Subject: Re: [RFA] Some libgcc headers are missing the runtime exception
Date: Mon, 12 Jul 2021 17:34:09 +0100 [thread overview]
Message-ID: <mpty2abebjy.fsf@arm.com> (raw)
In-Reply-To: <CAGWvnykEdbd2v5o=2LrD7QWzJxO7YCogSf9QuS0K3a-q1+D=qw@mail.gmail.com> (David Edelsohn's message of "Mon, 12 Jul 2021 12:15:52 -0400")
David Edelsohn <dje.gcc@gmail.com> writes:
> On Mon, Jul 12, 2021 at 11:58 AM Richard Sandiford
> <richard.sandiford@arm.com> wrote:
>>
>> David Edelsohn <dje.gcc@gmail.com> writes:
>> > On Fri, Jul 9, 2021 at 1:31 PM Richard Sandiford
>> > <richard.sandiford@arm.com> wrote:
>> >>
>> >> David Edelsohn <dje.gcc@gmail.com> writes:
>> >> > On Fri, Jul 9, 2021 at 12:53 PM Richard Sandiford via Gcc
>> >> > <gcc@gcc.gnu.org> wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> It was pointed out to me off-list that config/aarch64/value-unwind.h
>> >> >> is missing the runtime exception. It looks like a few other files
>> >> >> are too; a fuller list is:
>> >> >>
>> >> >> libgcc/config/aarch64/value-unwind.h
>> >> >> libgcc/config/frv/frv-abi.h
>> >> >> libgcc/config/i386/value-unwind.h
>> >> >> libgcc/config/pa/pa64-hpux-lib.h
>> >> >>
>> >> >> Certainly for the aarch64 file this was simply a mistake;
>> >> >> it seems to have been copied from the i386 version, both of which
>> >> >> reference the runtime exception but don't actually include it.
>> >> >>
>> >> >> What's the procedure for fixing this? Can we treat it as a textual
>> >> >> error or do the files need to be formally relicensed?
>> >> >
>> >> > I'm unsure what you mean by "formally relicensed".
>> >>
>> >> It seemed like there were two possibilities: the licence of the files
>> >> is actually GPL + exception despite what the text says (the textual
>> >> error case), or the licence of the files is plain GPL because the text
>> >> has said so since the introduction of the files. In the latter case
>> >> I'd have imagined that someone would need to relicense the code so
>> >> that it is GPL + exception.
>> >>
>> >> > It generally is considered a textual omission. The runtime library
>> >> > components of GCC are intended to be licensed under the runtime
>> >> > exception, which was granted and approved at the time of introduction.
>> >>
>> >> OK, thanks. So would a patch to fix at least the i386 and aarch64 header
>> >> files be acceptable? (I'm happy to fix the other two as well if that's
>> >> definitely the right thing to do. It's just that there's more history
>> >> involved there…)
>> >
>> > Please correct the text in the files. The files in libgcc used in the
>> > GCC runtime are intended to be licensed with the runtime exception and
>> > GCC previously was granted approval for that licensing and purpose.
>> >
>> > As you are asking the question, I sincerely doubt that ARM and Cavium
>> > intended to apply a license without the exception to those files. And
>> > similarly for Intel and FRV.
>>
>> FTR, I think only Linaro (rather than Arm) touched the aarch64 file.
>>
>> > The runtime exception explicitly was intended for this purpose and
>> > usage at the time that GCC received approval to apply the exception.
>>
>> Ack. Is the patch below OK for trunk and branches?
>
> I'm not certain whom you are asking for approval,
I was assuming it would need a global reviewer.
> but it looks good to me.
Thanks.
> It would be nice to add SPDX License Identifier at the top of the
> files as well, but that's not required.
Yeah, I agree that might a good thing to have, but TBH I try to keep
my involvement with licensing stuff to the bare minimum :-)
Richard
next prev parent reply other threads:[~2021-07-12 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mptlf6fjuo2.fsf@arm.com>
[not found] ` <mptpmvrjupn.fsf@arm.com>
[not found] ` <CAGWvnynKTb6tWHnN__WP=NZvbDDCSDK_7j9j8L74R-oM2eeSSQ@mail.gmail.com>
[not found] ` <mpta6mvjsw7.fsf@arm.com>
[not found] ` <CAGWvnymBxVsTeJgD6TsNFP=E1AKETb2WPc5rDWWFVMVRFE-3Kw@mail.gmail.com>
2021-07-12 15:58 ` Richard Sandiford
2021-07-12 16:15 ` David Edelsohn
2021-07-12 16:34 ` Richard Sandiford [this message]
2021-08-30 10:58 ` Thomas Schwinge
2021-08-30 11:46 ` Richard Biener
2021-08-31 10:01 ` Richard Sandiford
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=mpty2abebjy.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=law@redhat.com \
--cc=ramana.radhakrishnan@arm.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).