[Bug math/26563] New: libmvec_nonshared.a file removed, spec2017/525 build failed because of missing symbol _ZGVdN4v___exp_finite

[Bug math/26563] New: libmvec_nonshared.a file removed, spec2017/525 build failed because of missing symbol _ZGVdN4v___exp_finite

[skpgkp2 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=26563

            Bug ID: 26563
           Summary: libmvec_nonshared.a file removed, spec2017/525 build
                    failed because of missing symbol _ZGVdN4v___exp_finite
           Product: glibc
           Version: 2.31
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: math
          Assignee: unassigned at sourceware dot org
          Reporter: skpgkp2 at gmail dot com
  Target Milestone: ---

This issue appear while building spec2017/505 benchmark with AOCC(llvm)
compiler on Fedora 32. Commit d0007dc53cc83f22037bf6c7a297fa2e8066a335 removed
libmvec_nonshared.a library which define symbol _ZGVdN4v___exp_finite.

ld.lld: error: undefined symbol: _ZGVdN4v___exp_finite
>>> referenced by ld-temp.o
>>>               lto.tmp:(read_new_slice)
clang-9: error: linker command failed with exit code 1 (use -v to see
invocation)
specmake: ***
[/local/skpandey/gccwork/perfanalysis_525/cpu2017/benchspec/Makefile.defaults:337:
ldecod_r] Error 1
Error with make.ldecod_r 'specmake --output-sync --jobs=64 --load-average=64
build TARGET=ldecod_r':
  ----------------------------------------------------------------------------
  Please review this file:
   
"/local/skpandey/gccwork/perfanalysis_525/specbin/benchspec/CPU/525.x264_r/build/build_base_amd_rate_aocc200_rome_C.0000/make.ldecod_r.out"
  ----------------------------------------------------------------------------
  Command returned exit code 2
  Error with make!



commit d0007dc53cc83f22037bf6c7a297fa2e8066a335 (HEAD)
Author: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Date:   Tue Jul 16 11:29:06 2019 -0300

    Remove x64 _finite tests and references

    Remove _finite tests and references from x86_64.  Rather than calling
    __exp_finite, use exp directly (since it's the same entry point).

This checkin remove the file libmvec_nonshared.a and symbol become undefined.

commit 55d530114ef3513eb8588e31e3850f04ac608077 (HEAD)
Author: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Date:   Tue Jul 16 10:39:56 2019 -0300

bash-5.0$ readelf -s ./build-x86_64-linux/mathvec/libmvec_nonshared.a | grep
___exp_finite
    28: 0000000000000080     6 FUNC    GLOBAL DEFAULT    1
_ZGVbN2v___exp_finite
    30: 0000000000000090     6 FUNC    GLOBAL DEFAULT    1
_ZGVcN4v___exp_finite
    32: 00000000000000a0     6 FUNC    GLOBAL DEFAULT    1
_ZGVdN4v___exp_finite
    34: 00000000000000b0     6 FUNC    GLOBAL DEFAULT    1
_ZGVeN8v___exp_finite

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug math/26563] libmvec_nonshared.a file removed, spec2017/525 build failed because of missing symbol _ZGVdN4v___exp_finite

[skpgkp2 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=26563

Sunil Pandey <skpgkp2 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl.tools at gmail dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug math/26563] libmvec_nonshared.a file removed, spec2017/525 build failed because of missing symbol _ZGVdN4v___exp_finite

[joseph at codesourcery dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=26563

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The point of the removal was that all the references to *_finite symbols 
had already been removed from the glibc headers (bits/math-finite.h was 
removed), so nothing should be generating a reference to those symbols 
when building with the headers from a glibc where libmvec_nonshared.a 
doesn't provide corresponding wrappers.  So you need to find out what is 
using e.g. outdated glibc headers rather than those corresponding to the 
glibc version being used.  (Note that .o / .a files built with an old 
glibc can't be linked with a new glibc if they use symbols that have been 
obsoleted - there's backwards compatibility only for fully linked 
executables / shared libraries using such symbols, not unlinked object 
files.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.