> Date: Wed, 14 Aug 2024 22:12:23 -0500 > From: Jacob Bachmeyer <jcb62...@gmail.com>
> Done and pushed to Savannah as commit > ed301dbd6a3d769670503ccfda1ea31b58d02547. Please confirm that this > solves the problem. Confirmed*... > (Also note that you can now run DejaGnu from a Git checkout, simply use > the "runtest" in the Git working directory. Any problems with this are > bugs and will be fixed.) ...using this setup. Really nice! (* Confirmed that the commit fixes the problem, also as a sanity-check, verified that the combination with my patch does not mess things up.) As an aside for the gcc project only: by dejagnu now properly handling this issue, it also showed that there's a pruning-flaw with the g++ part testsuite (to wit, not intended to be covered by my patch which was only for libstdc++). This means that either gcc/testsuite/lib/prune.exp:prune_gcc_output has a flaw or is not applied for e.g. g++.dg/modules/global-3, g++.dg/modules/hello-1, g++.dg/modules/hello-2 and g++.dg/modules/iostream-1. I'll look into that. brgds, H-P
