public inbox for
 help / color / mirror / Atom feed
From: Gaius Mulley <>
To: Richard Biener <>
Cc:,  Jakub Jelinek <>,
	 "Joseph S. Myers" <>
Subject: Re: [PATCH] 0/19 modula-2 front end patches overview
Date: Mon, 14 Nov 2022 13:57:33 +0000	[thread overview]
Message-ID: <87wn7xwsdu.fsf@debian> (raw)
In-Reply-To: <> (Richard Biener's message of "Fri, 11 Nov 2022 15:02:15 +0100")

Richard Biener <> writes:

> On Mon, Oct 10, 2022 at 5:32 PM Gaius Mulley via Gcc-patches
> <> wrote:
>> Here are the latest modula-2 front end patches for review.
>> The status of the patches and their contents are also contained at:
>> where they are also broken down into topic groups.
>> In summary the high level changes from the last posting are:
>>    * the driver code has been completely rewritten and it is now based
>>      on the fortran driver and the c++ driver.  The gm2 driver adds
>>      paths/libraries depending upon dialect chosen.
>>    * the linking mechanism has been completely redesigned
>>      (As per
>>      Objects can be linked via g++.  New linking options
>>      are available to allow linking with/without a scaffold.
>>    * gcc/m2/ (rewritten).
>>    * gm2tools/ removed and any required functionality with the
>>      new linking mechanism has been moved into cc1gm2.
>> The gm2 testsuite has been extended to test project linking
>> options.
> Thanks for these improvements!

the front end feels alot cleaner now!

> The frontend specific parts are a lot to digest and I think it isn't
> too important to wait for the unlikely event that all of that gets a
> review.  I'm trusting you here as a maintainer and also based on the
> use of the frontend out in the wild.  I've CCed the other two RMs for
> their opinion on this.
> I hope to get to the driver parts that I reviewed the last time, I'd
> appreciate a look on the runtime library setup by somebody else.
> I think it's important to get this (and the rust frontend) into the tree before
> Christmas holidays so it gets exposed to the more weird treatment of some
> of our users (build wise).  This way we can develop either a negative or
> positive list of host/targets where to disable the new frontends.

great news thanks - yes this makes sense,


  reply	other threads:[~2022-11-14 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 15:31 Gaius Mulley
2022-10-12 12:31 ` Rainer Orth
2022-10-12 13:06   ` Gaius Mulley
2022-11-11 14:02 ` Richard Biener
2022-11-14 13:57   ` Gaius Mulley [this message]
2022-11-30 13:29   ` Richard Biener
2022-12-05 13:33     ` Gaius Mulley

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wn7xwsdu.fsf@debian \ \ \ \ \ \

* 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).