[Bug driver/122265] New: [16 Regression] many SPECCPU 2017 and SPECCPU 2006 benchmarks fail to link after g:e63cf4b130b86dd7dde1bf499d3d40faca10ea2e

[tnfchris at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122265

            Bug ID: 122265
           Summary: [16 Regression] many SPECCPU 2017 and SPECCPU 2006
                    benchmarks fail to link after
                    g:e63cf4b130b86dd7dde1bf499d3d40faca10ea2e
           Product: gcc
           Version: 16.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tnfchris at gcc dot gnu.org
  Target Milestone: ---

Since g:e63cf4b130b86dd7dde1bf499d3d40faca10ea2e

I'm getting failures trying to link various SPECCPU binaries using glibc
50351e05707f982c06c6d4d7c8fc819f6a5f66f5.

The errors are all:

../run_peak_refrate_ab.0000/omnetpp_r_peak.ab: symbol lookup error:
/lib/aarch64-linux-gnu/libpthread.so.0: undefined symbol: __libc_pthread_init,
version GLIBC_PRIVATE

in intrate as an example failing benchmarks are

520.omnetpp_r
523.xalancbmk_r
531.deepsjeng_r
541.leela_r