Problems due to platform binutils

Hi

Bah, clicked send before I'd finished.

I'm looking at some Valgrind testcase failures when I run the testsuite 
on the GCC build server farm FreeBSD machines. I haven't yet asked how 
the servers were installed. uname says

16.0-CURRENT FreeBSD 16.0-CURRENT main-n284729-ccc235fe0229 GENERIC arm64

and


16.0-CURRENT FreeBSD 16.0-CURRENT main-n284742-7b6be0014a4e GENERIC amd64

They both have GNU binutils and platform binutils installed

pkg info | grep binutils
aarch64-binutils-2.44,1        GNU binary tools
binutils-2.44,1                GNU binary tools
elfutils-0.187_3               Library for manipulating ELF files and 
partial implementation of binutils

(amd64-binutils-2.44 on the amd64 machine).

clang seems to want to use this ld.bfd ( 
/usr/local/bin/aarch64-unknown-freebsd16.0-ld) rather than /usr/bin/ld 
(which is ld.lld).

I did see one issue because of this which I've now fixed. The 
alternative is to use something like LDFLAGS=-fuse-ld=/usr/bin/ld.

The other thing that I'm seeing is quite a few failures that look like 
they are because the servers were installed from source .

For instance

--- annotate_barrier.stderr.exp2025-11-22 18:33:32.333659000 +0000
+++ annotate_barrier.stderr.out2026-04-04 16:46:36.872126000 +0000
@@ -25,7 +25,7 @@
Conflicting store by thread 2 at 0x........ size 4
    at 0x........: threadfunc (annotate_barrier.c:?)
    by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-   by 0x........: start_thread
+   by 0x........: ??? (worktrees/main/lib/libthr/thread/thr_create.c:299)
Address 0x........ is at offset 0 from 0x......... Allocation context:
    at 0x........: malloc (vg_replace_malloc.c:...)
    by 0x........: barriers_and_races (annotate_barrier.c:?)

That one is a but odd, I wonder why I'm getting file and line but not 
function name.

We already have a lot of filtering to make the results as platform 
independent as possible. Other than extending that filtering to cover 
all these extra cases does anyone else have any experience with this 
kind of issue on FreeBSD?

There are also massif and helgrind failures that I don't yet understand.

A+

Paul