From: Gaius Mulley <gaius.mulley@southwales.ac.uk>
To: Matthias Klose <doko@ubuntu.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)
Date: Wed, 20 Nov 2019 10:10:00 -0000 [thread overview]
Message-ID: <875zjej1yk.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <2038b684-74be-969a-5da0-60832950ea56@ubuntu.com> (Matthias Klose's message of "Thu, 18 Jul 2019 22:08:16 +0200")
Matthias Klose <doko@ubuntu.com> writes:
> On 08.07.19 23:19, Matthias Klose wrote:
>> On 14.06.19 15:09, Gaius Mulley wrote:
>>>
>>> Hello,
>>>
>>> here is version two of the patches which introduce Modula-2 into the
>>> GCC trunk. The patches include:
>>>
>>> (*) a patch to allow all front ends to register a lang spec function.
>>> (included are patches for all front ends to provide an empty
>>> callback function).
>>> (*) patch diffs to allow the Modula-2 front end driver to be
>>> built using GCC Makefile and friends.
>>>
>>> The compressed tarball includes:
>>>
>>> (*) gcc/m2 (compiler driver and lang-spec stuff for Modula-2).
>>> Including the need for registering lang spec functions.
>>> (*) gcc/testsuite/gm2 (a Modula-2 dejagnu test to ensure that
>>> the gm2 driver is built and can understands --version).
>>>
>>> These patches have been re-written after taking on board the comments
>>> found in this thread:
>>>
>>> https://gcc.gnu.org/ml/gcc-patches/2013-11/msg02620.html
>>>
>>> it is a revised patch set from:
>>>
>>> https://gcc.gnu.org/ml/gcc-patches/2019-06/msg00220.html
>>>
>>> I've run make bootstrap and run the regression tests on trunk and no
>>> extra failures occur for all languages touched in the ChangeLog.
>>>
>>> I'm currently tracking gcc trunk and gcc-9 with gm2 (which works well
>>> with amd64/arm64/i386) - these patches are currently simply for the
>>> driver to minimise the patch size. There are also > 1800 tests in a
>>> dejagnu testsuite for gm2 which can be included at some future time.
>>
>> I had a look at the GCC 9 version of the patches, with a build
>> including a make
>> install. Some comments:
>
> A look at the licenses:
>
> libgm2/p2c/*: GPL 3+
> libgm2/libiso/*: LGPL 2.1+
> libgm2/libmin/libc.c: GPL 3+
> libgm2/liblog/*: LGPL 2.1+
> libgm2/libpim/*: LGPL 2.1+
> libgm2/libpim/Selective.c: GPL 3+
> libgm2/libpim/wrapc.c: GPL 3+
> libgm2/libpth/*: LGPL 2.1+
>
> gcc/gm2/ulm-lib-gm2/* GPL 3+, Ulm copyright holder?
>
> gcc/gm2/gm2-libs/*.def GPL 3+
> gcc/gm2/gm2-libs/Break.def LGPL 2.1+
> gcc/gm2/gm2-libs/*.mod LGPL 2.1+
> gcc/gm2/gm2-libs/Builtins.mod GPL 3+
>
> I didn't look at everything in gcc/gm2, however it's not clear for me when a
> file is LGPL or GPL. And at least in gm2-libs, it seems to be mixed randomly.
> First I thought all definition modules were GPL, and implementation modules were
> LGPL, but that's not the case.
>
> So currently all code linked with the runtime libs becomes GPL 3+?
>
> For the ulm lib, the files mention the Ulm university as the copyright holder,
> but it's not clear which license these files had before they were imported.
>
> libgm2 seems to be mostly LGPL except for two files. Intended?
>
> Matthias
Hi Matthias,
many thanks for the analysis. I've now:
* removed all gnu pth code and rewritten the coroutine libraries to
use libgcc/gthr.h.
* removed all Univ Ulm libraries
* changed all remaining library code to use GPL3+ gcc runtime
extensions
* checked all compiler code is GPL3
(on the master branch of gm2)
[I've still working on the testsuite]
regards,
Gaius
next prev parent reply other threads:[~2019-11-20 10:07 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:10 Gaius Mulley
2019-06-29 10:15 ` Richard Sandiford
2019-06-29 12:52 ` Richard Biener
2019-06-29 20:29 ` Gaius Mulley
2019-06-29 18:08 ` Segher Boessenkool
2019-07-02 0:18 ` Gaius Mulley
2019-07-03 8:41 ` Rainer Orth
2019-07-08 15:20 ` Gaius Mulley
2019-07-08 15:31 ` Rainer Orth
2019-07-09 9:25 ` Rainer Orth
2019-07-09 11:41 ` Gaius Mulley
2019-07-10 11:50 ` Rainer Orth
2019-07-08 15:41 ` Gaius Mulley
2019-07-08 21:21 ` Matthias Klose
2019-07-09 6:37 ` Matthias Klose
2019-07-09 19:50 ` Gaius Mulley
2019-07-09 21:35 ` Matthias Klose
2019-07-10 17:56 ` Matthias Klose
2019-07-10 20:18 ` Gaius Mulley
2019-07-10 20:38 ` Matthias Klose
2019-07-10 21:16 ` Gaius Mulley
2019-07-09 9:56 ` Matthias Klose
2019-07-09 12:14 ` Gaius Mulley
2019-07-09 13:24 ` Matthias Klose
2019-07-09 13:49 ` Gaius Mulley
2019-07-09 16:23 ` Matthias Klose
2019-07-09 17:22 ` Gaius Mulley
2019-07-09 12:31 ` Rainer Orth
2019-07-09 15:57 ` Gaius Mulley
2019-07-09 17:32 ` Matthias Klose
2019-07-10 20:45 ` Gaius Mulley
2019-07-10 12:11 ` Rainer Orth
2019-07-09 21:36 ` Matthias Klose
2019-07-10 17:11 ` Matthias Klose
2019-07-10 20:49 ` Gaius Mulley
2019-07-11 7:57 ` Matthias Klose
2019-07-11 12:12 ` Gaius Mulley
2019-07-11 16:40 ` Segher Boessenkool
2019-07-11 17:26 ` Gaius Mulley
2019-07-12 15:41 ` Segher Boessenkool
2019-07-12 18:35 ` Gaius Mulley
2019-07-18 20:15 ` Matthias Klose
2019-11-20 10:10 ` Gaius Mulley [this message]
2019-07-19 14:22 ` Matthias Klose
2019-07-20 21:41 ` Matthias Klose
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=875zjej1yk.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius.mulley@southwales.ac.uk \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
/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).