Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)

[Gaius Mulley <gaius.mulley@southwales.ac.uk>]

[-- Attachment #1: Type: text/plain, Size: 2616 bytes --]

Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:

> Hi Gaius,
>
>> 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 meant to give a build with gm2 included a try on Solaris, but ended up
> pretty much confused:
>
> * I've started with the gm2 repo on savannah.  Running the combine-trees
>   script on master tried to combine gm2 with gcc 4.7.4.  Trying again
>   with configure --with-gcc=none (no branch, for trunk?) didn't work
>   either (don't remember the details off-hand).
>
> * Next, I discovered and tried the gcc_trunk branch there.  While it
>   matches the patch set you sent here, it lacks most of the compiler
>   proper, which only lives on master!?  In addition, the patches in
>   there lack support for building libgm2.  Those are present on the
>   master branch (which has both trunk and trunc in
>   gcc-versionno/gcc/gm2/patches/gcc).  I tried to merge the trees and
>   apply the patches manually, but failed again later.
>
> At this point, I gave up.  Am I missing something fundamental here?
>
> Thanks.
>         Rainer

Hi Rainer,

it rather depends upon what you want, if you want the latest complete
gm2 grafting onto the svn gcc trunk then these two scripts will create a
patched tree and also rebuild gm2.


[-- Attachment #2: build scripts for gcc trunk --]
[-- Type: application/gzip, Size: 1110 bytes --]

[-- Attachment #3: Type: text/plain, Size: 748 bytes --]


[however please be careful with the scripts - they do assume that
everything will be built in $HOME/GM2 - read and adapt as necessary].

These will build a complete gm2 (from the master) - whereas the gcc_trunk
branch is used to track the patches which are posted to gcc-patches
(which are currently minimal and just build the gm2 driver).

There are snapshots available for 9.1.0, 8.2.0, 6.4.0 as well as back to
the older 4.7.4 series.

http://floppsie.comp.glam.ac.uk/download/c/gcc-9.1.0+gm2-git-latest.tar.gz
http://floppsie.comp.glam.ac.uk/download/c/gcc-8.2.0+gm2-git-latest.tar.gz
http://floppsie.comp.glam.ac.uk/download/c/gcc-6.4.0+gm2-git-latest.tar.gz

these tarballs are created using combine-trees, hope this helps,


regards,
Gaius