From: Gaius Mulley <gaiusmod2@gmail.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [PATCH v3 0/19] modula-2 front end patches overview
Date: Tue, 06 Dec 2022 14:52:06 +0000 [thread overview]
Message-ID: <E1p2ZIk-004Qjy-EF@lancelot> (raw)
Here are the latest modula-2 front end patches. Since the posting in
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603161.html
I've rewritten the python3 documentation scripts (feedback from
patchset 16) and applied all the suggestions from the feedback in
patchset 15 (gm2-lang.cc).
All the patches are can also be at:
https://splendidisolation.ddns.net/public/modula2/patchsummary.html
which contains the status of the patch, their contents and testing
summary.
Thanks for the feedback - and clean up suggestions!
regards,
Gaius
Patch Summary
=============
The gm2 driver program and top level makefile infrastructure
[PATCH v3] 1/19: changes outside gcc/m2, libgm2 and gcc/testsuite.
[PATCH v3] 2/19: Make-lang.in
[PATCH v3] 3/19: gm2 driver files.
The libraries /libgm2
[PATCH v3] 4/19: libgm2/libm2pim contents
[PATCH v3] 5/19: libgm2/libm2iso contents
[PATCH v3] 6/19: libgm2/libm2min contents
[PATCH v3] 7/19: libgm2/libm2log contents
[PATCH v3] 8/19: libgm2 contents
Modula-2 plugin
[PATCH v3] 9/19: plugin source files
Modula-2 to gimple interface
[PATCH v3] 10/19: gimple interface header files *.h and *.def
[PATCH v3] 11/19: gimple interface *[a-d]*.cc
[PATCH v3] 12/19: gimple interface *[e-f]*.cc
[PATCH v3] 13/19: gimple interface *[g-m]*.cc
[PATCH v3] 14/19: gimple interface remainder
Lexical analysis (flex), lang hooks and debug tree module
[PATCH v3] 15/19: cc1gm2 additional non modula2 source files
Linking bootstrap tool and documentation build script
[PATCH v3] 16/19: bootstrap and documentation tools
Testsuite and remaining files
[PATCH v3] 17/19: dejagnu expect library scripts.
[PATCH v3] 18/19: remainder of the files for the compiler and libraries. (not posted)
[PATCH v3] 19/19: modula2 testsuite. (not posted)
reply other threads:[~2022-12-06 14:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1p2ZIk-004Qjy-EF@lancelot \
--to=gaiusmod2@gmail.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).