public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gaius Mulley <gaiusmod2@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: Modula-2: merge followup (brief update on the progress of the new linking implementation)
Date: Mon, 27 Jun 2022 08:24:49 +0100	[thread overview]
Message-ID: <87h746va9q.fsf@debian> (raw)
In-Reply-To: <595F2F1F-468D-49AF-B135-CA8845148049@gmail.com> (Richard Biener's message of "Fri, 17 Jun 2022 21:02:09 +0200")


Hi,

all 11k regression tests pass with the new linking implementation (on
devel/m2link).  I plan to migrate the patches back to devel/modula-2 and
then remove devel/m2link.  Thereafter {polish,test} and generate new
patch sets.  Thanks for the clear explanation on how the dynamic
scaffold should work!

regards,
Gaius

  reply	other threads:[~2022-06-27  7:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 19:15 Gaius Mulley
2022-06-17 17:08 ` Gaius Mulley
2022-06-17 19:02   ` Richard Biener
2022-06-27  7:24     ` Gaius Mulley [this message]
2022-07-09 10:31 Gaius Mulley
2022-07-11  8:21 ` Rainer Orth
2022-07-11 11:14   ` Rainer Orth
2022-07-11 15:06   ` Gaius Mulley
2022-07-11 20:36     ` Rainer Orth
2022-07-12 12:32       ` Gaius Mulley
2022-07-12 14:16         ` Rainer Orth
2022-07-25  9:42           ` Gaius Mulley
2022-07-26  7:45             ` Rainer Orth
2022-08-30 11:03 ` Gaius Mulley
2022-08-30 12:44   ` Martin Liška
2022-08-30 15:36     ` Gaius Mulley
2022-08-31  9:54       ` Martin Liška
2022-08-31 13:19         ` Gaius Mulley
2022-08-31 13:25           ` Martin Liška
2022-09-01 12:22             ` Gaius Mulley
2022-09-07 12:29             ` Martin Liška
2022-09-08 15:52               ` Gaius Mulley
2022-09-09 12:16                 ` Martin Liška
2022-09-09 15:40                   ` 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:
  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=87h746va9q.fsf@debian \
    --to=gaiusmod2@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.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).