bogus FAILs from mmix ld testsuite

[Alan Modra]

On Mon, Nov 17, 2025 at 08:20:35PM -0500, Hans-Peter Nilsson wrote:
> On Tue, 18 Nov 2025, Alan Modra wrote:
> > On Mon, Nov 17, 2025 at 05:04:47PM +0100, Jan Beulich wrote:
> > > On 17.11.2025 16:27, Andreas Schwab wrote:
> > > > On Nov 17 2025, Jan Beulich wrote:
> > > > 
> > > >> .../ld/.libs/ld-new: tmpdir/bpo-7.o:(.text+0x2): undefined reference to `areg'
> > > >> failed with: <.../ld/.libs/ld-new: tmpdir/bpo-7.o:(.text+0x2): undefined reference to `areg'>, expected: <^[^c][^h][^i][^l][^d].* undefined reference to `areg'$>
> > > > 
> > > > What are the real first five characters of the message?  Because, if any
> > > > of them happens to match a character in "child" the match will fail.
> > > 
> > > The path starts with /home/jbeulich. (Also this wouldn't change when re-running
> > > "make check", I suppose.
> > 
> > The 'h' in /home doesn't match the regex.
> > 
> > > Yet as said, the re-run doesn't hit the same FAILs.)
> > 
> > Are you sure about that?  I consistently get fails if building mmix
> > with --enable-shared, because then the ld-new file name is given as an
> > absolute path.  My default --disable-shared mmix builds report
> > "./ld-new".
> 
> The obvious question needs to be pondered: if that observation 
> is correct, isn't that difference in output unwanted, perhaps 
> even to be considered a bug by itself?

No, I don't think so.  If there is any obvious bug here it's in the
test trying to exclude "child" for some reason, and doing so in a way
that matches much more than just "child".  I'm guessing you hit some
sort of dejagnu/tcl error at some stage, and didn't want that hidden.

-- 
Alan Modra