From: Alexandre Oliva <oliva@adacore.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <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>,
<mikestump@comcast.net>, <nathan@acm.org>
Subject: Re: 'g++.dg/modules/modules.exp': don't leak local 'unsupported' proc [PR108899]
Date: Thu, 30 Mar 2023 04:00:03 -0300 [thread overview]
Message-ID: <orr0t6n2q4.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <87o7ob2usn.fsf@euler.schwinge.homeip.net> (Thomas Schwinge's message of "Wed, 29 Mar 2023 21:59:20 +0200")
On Mar 29, 2023, Thomas Schwinge <thomas@codesourcery.com> wrote:
> I assume that the second UNSUPPORTED:
> -UNSUPPORTED: g++.dg/modules/explicit-bool-1_b.C -std=c++17
> ... disappears is the intention of this patch?
Yup
> But surely the curly braces in:
> -UNSUPPORTED: g++.dg/modules/explicit-bool-1_a.H -std=c++17
> +UNSUPPORTED: {g++.dg/modules/explicit-bool-1_a.H -std=c++17}
> ... are not intentional? (Alexandre?)
Unintended indeed, will look, thanks for letting me know
> But worse, the latter also "bleeds into" all other testing
Eeek
Yeah, that's a much bigger problem indeed.
> ..., this isn't sufficient. Instead, we should undo the 'rename' at the
> end of 'g++.dg/modules/modules.exp'. OK to push the attached
> "'g++.dg/modules/modules.exp': don't leak local 'unsupported' proc [PR108899]"
> after proper testing?
Ooh, nice, I didn't know how to drop the renaming after we were done
with it, and hoped the end of the .exp would have accomplished that by
ending a scope. Jakub had already pointed out this wasn't the case, but
I didn't realize, when he did, that this would carry over onto other
modules.
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...
diff --git a/gcc/testsuite/g++.dg/modules/modules.exp b/gcc/testsuite/g++.dg/modules/modules.exp
index 80aa392bc7f3b..6fd5050cef79b 100644
--- a/gcc/testsuite/g++.dg/modules/modules.exp
+++ b/gcc/testsuite/g++.dg/modules/modules.exp
@@ -319,15 +319,11 @@ cleanup_module_files [find $DEFAULT_REPO *.gcm]
# so that, after an unsupported result in dg-test, we can skip rather
# than fail subsequent related tests.
set module_do {"compile" "P"}
-if { [info procs unsupported] != [list] \
- && [info procs saved-unsupported] == [list] } {
- rename unsupported saved-unsupported
-
- proc unsupported { args } {
- global module_do
- lset module_do 1 "N"
- return [saved-unsupported $args]
- }
+rename unsupported modules-saved-unsupported
+proc unsupported { args } {
+ global module_do
+ lset module_do 1 "N"
+ return [eval modules-saved-unsupported $args]
}
# not grouped tests, sadly tcl doesn't have negated glob
@@ -412,4 +408,10 @@ foreach src [lsort [find $srcdir/$subdir {*_a.[CHX}]] {
}
}
+# Restore the original unsupported proc, lest it will affect
+# subsequent test runs, or even fail renaming if we run modules.exp
+# for multiple targets/multilibs/options.
+rename unsupported {}
+rename modules-saved-unsupported unsupported
+
dg-finish
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2023-03-30 7:00 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 ` Alexandre Oliva [this message]
2023-03-30 9:39 ` 'g++.dg/modules/modules.exp': don't leak local 'unsupported' proc [PR108899] Thomas Schwinge
2023-03-30 13:51 ` Alexandre Oliva
2023-03-31 18:52 ` Jason Merrill
2023-04-01 18:06 ` Mike Stump
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=orr0t6n2q4.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=mikestump@comcast.net \
--cc=nathan@acm.org \
--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).