On Wed, 2025-09-10 at 18:23 +0100, Richard Earnshaw (lists) wrote: > On 10/09/2025 14:06, Jeff Law wrote: > > > > > > On 9/10/25 4:23 AM, Iain Sandoe wrote: > > > > > Now we have this facility - and it is firing on my testboxes > > > (since i use this > > > script to post-process [per .sum file for stability]) - I looked > > > through a few of > > > the reported cases and they seem genuiene - but particularly in > > > respect of > > > dg-final ones, hard to see how they can be disambiguated without > > > we make > > > dg-final able to add some tag to differentiate. > > > > > > are there any plans to deal with this new reported data? > > > if not, I’d welcome a switch on the script - so that one could at > > > least elect > > > only to report new dups .. > > Yea. I need to go through my results as well, it was a bit > > overwhelming. > > > > Given the filename, opt flags and scan string are in the testname, > > it's a bit surprising to hear that the dg-finals are triggering :( > > > > jeff > > With Christophe's patch from earlier today I see ~100 dup tests in > gcc.sum for arm (for two variants, so probably about 50). But even > that is an overstatement of the number of dups. The first one I > looked at is a real bug in the testsuite (scanning for sadd8 for a > test that should output sadd16) and that test is run with 7 different > flag combinations. > > So it's already finding real problems. > > I also need to investigate why the framework is failing to find > python3, or at least why it thinks that python 3.13.3 is too old.
What failure are you seeing? (I wonder if something is truncating the version info to just "3.1"?) If it's failing in check_effective_target_recent_python3, that looks like it properly handles multidigit minor versions; what's the output from: python3 -c "import sys; print(repr(sys.version_info))" Dave
