From: Mike Stump <mikestump@comcast.net>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
Richard Biener <rguenther@suse.de>,
Jason Merrill <jason@redhat.com>,
ro@cebitec.uni-bielefeld.de, nathan@acm.org
Subject: Re: 'g++.dg/modules/modules.exp': don't leak local 'unsupported' proc [PR108899]
Date: Sat, 1 Apr 2023 11:06:08 -0700 [thread overview]
Message-ID: <BC538E96-5B4E-442D-B13A-98A9AFC35A71@comcast.net> (raw)
In-Reply-To: <or1ql6mjob.fsf@lxoliva.fsfla.org>
On Mar 30, 2023, at 6:51 AM, Alexandre Oliva <oliva@adacore.com> wrote:
>
> On Mar 30, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
>
>> If we're dropping the renaming, I suppose we could also revert Jakub's
>> change. I suppose this patch will take care of it, pending testing...
>
> Regstrapped on x86_64-linux-gnu and also tested on arm-vx7r2 (with
> gcc-12), where I used to get fails after an unsupported modules.exp
> test, but there are no curly braces in the log files after the patch.
> Ok to install?
Ok.
next prev parent reply other threads:[~2023-04-01 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 6:55 [PATCH] Skip module_cmi_p and related unsupported module test Alexandre Oliva
2023-02-20 4:27 ` Jason Merrill
2023-02-22 17:33 ` Alexandre Oliva
2023-02-23 14:18 ` [PATCH] testsuite: Fix up modules.exp [PR108899] Jakub Jelinek
2023-02-23 15:02 ` Richard Biener
2023-03-29 19:59 ` 'g++.dg/modules/modules.exp': don't leak local 'unsupported' proc [PR108899] (was: [PATCH] testsuite: Fix up modules.exp [PR108899]) Thomas Schwinge
2023-03-30 7:00 ` 'g++.dg/modules/modules.exp': don't leak local 'unsupported' proc [PR108899] Alexandre Oliva
2023-03-30 9:39 ` Thomas Schwinge
2023-03-30 13:51 ` Alexandre Oliva
2023-03-31 18:52 ` Jason Merrill
2023-04-01 18:06 ` Mike Stump [this message]
2023-04-05 7:47 ` Thomas Schwinge
2023-04-06 2:38 ` Alexandre Oliva
2023-04-06 20:11 ` Thomas Schwinge
2023-04-06 23:40 ` Alexandre Oliva
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=BC538E96-5B4E-442D-B13A-98A9AFC35A71@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=nathan@acm.org \
--cc=oliva@adacore.com \
--cc=rguenther@suse.de \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=thomas@codesourcery.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).