From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) by sourceware.org (Postfix) with ESMTPS id 7D220382CCA9 for ; Tue, 7 Jun 2022 07:43:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7D220382CCA9 Received: by mail-wr1-x432.google.com with SMTP id x17so22884782wrg.6 for ; Tue, 07 Jun 2022 00:43:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :mime-version; bh=Y13rnO48VMVoWESUACgfGyfsdWx9ou/EzrKu7Enjq/o=; b=itPSRc1Q8g0cx10sFLkmG8n9tt0me3ofhKsPrwKExjuOUOMZVRkJ+PjyBGQZ5v9Xr7 9ODI2sJTXdnYzplxhIX/v0j//+m8XsvGWvKazdGdvG7U0gnkPFWFlOAnxrjFBU5FwMAT d9P6vAcAz6qjx5354/OHOxFqyJJvMtIIvK+Ah4V7HL6K7bMaPo8fS29B6hpc09aqVKGv 9i7B4/0at0np1Dhdxd65T99rHFdYQ6aYZqU04Rdvbzd7arcKSFuHE8/m34dhmoh3uoOi +GE1pjx+HXvCSi2OTsk/qni5870UaxxZbzx6AAFDsymzehdf1yVW1l0O9At00NdGwYI5 tMWA== X-Gm-Message-State: AOAM532XgmnXC52SecbTpJCn1QSJFjNKqrVx6Hz5gklu03MQ6oui88zW neK1NbA5Qi9aPTTif8tT7yzR4PW483M= X-Google-Smtp-Source: ABdhPJxF8uISSgIPKgH5FYY1BQgd0rnYdBJzE7UIpMiV8+ivZe+O0hlDqRLdIVJBb9o0CLRke52V0g== X-Received: by 2002:a05:6000:1448:b0:20c:7be8:c2e with SMTP id v8-20020a056000144800b0020c7be80c2emr25196378wrx.692.1654587780172; Tue, 07 Jun 2022 00:43:00 -0700 (PDT) Received: from lancelot (host31-54-80-187.range31-54.btcentralplus.com. [31.54.80.187]) by smtp.gmail.com with ESMTPSA id t15-20020a05600c198f00b003942a244f40sm24793932wmq.25.2022.06.07.00.42.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Jun 2022 00:42:59 -0700 (PDT) Received: from gaius by lancelot with local (Exim 4.94.2) (envelope-from ) id 1nyTre-0005WK-Cd; Tue, 07 Jun 2022 08:42:58 +0100 From: Gaius Mulley To: gcc-patches@gcc.gnu.org Subject: Modula-2: merge followup re: patch-set 01..09 Date: Tue, 07 Jun 2022 08:42:58 +0100 Message-ID: <87leu8q5q5.fsf@debian> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, KAM_NUMSUBJECT, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2022 07:43:03 -0000 thank you to the reviewers of the patch sets 01 though 09. As a brief followup/summary I propose rewriting linking as per Richard's suggestion: https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595782.html Aside from the many technical advantages, logistically it also means: * the gm2 driver code becomes similar to existing front end drivers. * allowing the next set of patches to be smaller and easier to review. [The driver will be posted separate to the gimple interface] Would it be ok to open up a short term branch devel/m2link to accomodate these disruptive code changes, or would a private branch be more appropriate? Currently the runtime changes have been completed. regards, Gaius