Summary: | sci-libs/rocBLAS-5.1.3-r1 QA Notice: Unrecognized ELF file(s) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alessandro Barbieri <lssndrbarbieri> |
Component: | Current packages | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | xgreenlandforwyy |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 891001 | ||
Bug Blocks: | |||
Attachments: |
emerge_info
rocBLAS-4.0.0-r2:20210612-165931.logx.xz |
Description
Alessandro Barbieri
2021-06-13 23:07:41 UTC
Created attachment 715830 [details]
emerge_info
emerge --info
Created attachment 715833 [details]
rocBLAS-4.0.0-r2:20210612-165931.logx.xz
build log (compressed because it exceeds attachment limit, use 'xzless' to read it)
* QA Notice: Unrecognized ELF file(s): * * UNKNOWN_TYPE;/usr/lib64/rocblas/library/Kernels.so-000-gfx803.hsaco;Kernels.so-000-gfx803.hsaco;;; * UNKNOWN_TYPE;/usr/lib64/rocblas/library/TensileLibrary_gfx906.co;TensileLibrary_gfx906.co;;; * UNKNOWN_TYPE;/usr/lib64/rocblas/library/TensileLibrary_gfx900.co;TensileLibrary_gfx900.co;;; * UNKNOWN_TYPE;/usr/lib64/rocblas/library/TensileLibrary_gfx803.co;TensileLibrary_gfx803.co;;; * UNKNOWN_TYPE;/usr/lib64/rocblas/library/TensileLibrary_gfx908.co;TensileLibrary_gfx908.co;;; The TensileLibrary_gfx[0-9]*.co is tensile code object libraries for heterogeneous computing, containing assembly GPU kernels. See https://github.com/ROCmSoftwarePlatform/Tensile/wiki/TensileCreateLibrary#code-object-libraries for more information. It does have a unknown ELF format, and in the future it may have a name of its own ,I guess. Does it make sense to move these .co files out of /usr/lib64? These code object files can be moved to another directory, but where should it go? (In reply to Wu Yiyang from comment #6) > These code object files can be moved to another directory, but where should > it go? How about /usr/share/rocblas ? > (In reply to Wu Yiyang from comment #6) > > These code object files can be moved to another directory, but where should > > it go? > > How about /usr/share/rocblas ? /usr/share/rocblas/library is better, I think.(In reply to Benda Xu from comment #7) Shall we change it in rocBLAS-4.1? Also, for the upcoming rocBLAS-4.1 in https://github.com/gentoo/sci/pull/1102, enabling benchmark will install /usr/lib64/librocblas_fortran_client.so, which is a statically linked shared object file, and causes QA Notice: The following shared libraries lack NEEDED entries. (In reply to Wu Yiyang from comment #8) > > (In reply to Wu Yiyang from comment #6) > > > These code object files can be moved to another directory, but where should > > > it go? > > > > How about /usr/share/rocblas ? > > /usr/share/rocblas/library is better, I think.(In reply to Benda Xu from > comment #7) > > Shall we change it in rocBLAS-4.1? OK, let's do it. (In reply to Wu Yiyang from comment #9) > Also, for the upcoming rocBLAS-4.1 in > https://github.com/gentoo/sci/pull/1102, enabling benchmark will install > /usr/lib64/librocblas_fortran_client.so, which is a statically linked shared > object file, and causes QA Notice: The following shared libraries lack > NEEDED entries. Can we find the static flags and replace it with a dynamical one? (In reply to Benda Xu from comment #11) > (In reply to Wu Yiyang from comment #9) > > Also, for the upcoming rocBLAS-4.1 in > > https://github.com/gentoo/sci/pull/1102, enabling benchmark will install > > /usr/lib64/librocblas_fortran_client.so, which is a statically linked shared > > object file, and causes QA Notice: The following shared libraries lack > > NEEDED entries. > > Can we find the static flags and replace it with a dynamical one? The generation command run by ninja is : /opt/gentoo/usr/bin/x86_64-pc-linux-gnu-gfortran -fPIC -O2 -pipe -Wl,-O1 -Wl,--as-needed -shared -Wl,-soname,librocblas_fortran_client.so -o test.so clients/CMakeFiles/rocblas_fortran.dir/__/library/include/rocblas_module.f90.o clients/CMakeFiles/rocblas_fortran_client.dir/include/rocblas_fortran.f90.o clients/CMakeFiles/rocblas_fortran_client.dir/include/rocblas_fortran_tensile.f90.o Removing '-Wl,--as-needed' can dynamically link librocblas_fortran_client.so, but the size is bigger (In reply to Wu Yiyang from comment #12) > Removing '-Wl,--as-needed' can dynamically link > librocblas_fortran_client.so, but the size is bigger According to https://wiki.gentoo.org/wiki/Project:Quality_Assurance/As-needed, this '--as-needed' flag is part of Gentoo QA... Moving code object into /usr/share cannot stop portage throwing this QA notice. Just ignore it. Dear QA Team: We would like to hear your recommendation. rocBLAS is an AMD framework of linear algebraic computation kernels offloaded to GPUs. The compiled kernel is in an ELF format portage QA is not aware of. Yours, Benda tinderbox has reproduced this issue with version 4.3.0 - Updating summary. tinderbox has reproduced this issue with version 5.0.2 - Updating summary. clang-stricter_tinderbox has reproduced this issue with version 5.1.3 - Updating summary. libarchive_tinderbox has reproduced this issue with version 5.1.3-r1 - Updating summary. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=bde2a895cf520687dce7a8e92601041a37529ba0 commit bde2a895cf520687dce7a8e92601041a37529ba0 Author: Yiyang Wu <xgreenlandforwyy@gmail.com> AuthorDate: 2023-02-02 14:53:44 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-15 08:38:53 +0000 ELF: add EM_AMDGPU entry With this, portage is able to detect AMDGPU machine code elf object. Bug: https://bugs.gentoo.org/795825 Signed-off-by: Yiyang Wu <xgreenlandforwyy@gmail.com> Closes: https://github.com/gentoo/portage/pull/983 Signed-off-by: Sam James <sam@gentoo.org> NEWS | 3 +++ lib/portage/dep/soname/multilib_category.py | 2 ++ lib/portage/util/elf/constants.py | 1 + 3 files changed, 6 insertions(+) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=106f3ae650ca0e76c6fb59e1846912228f4afa72 commit 106f3ae650ca0e76c6fb59e1846912228f4afa72 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-02-17 09:14:38 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-17 09:14:38 +0000 NEWS: add bug reference for AMDGPU support Bug: https://bugs.gentoo.org/795825 Signed-off-by: Sam James <sam@gentoo.org> NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd8ade10313d72cb0e3dd2229df02e0ea8681daa commit cd8ade10313d72cb0e3dd2229df02e0ea8681daa Author: Sam James <sam@gentoo.org> AuthorDate: 2023-02-26 22:01:01 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-26 22:01:10 +0000 sys-apps/portage: add 3.0.45 Bug: https://bugs.gentoo.org/891001 Bug: https://bugs.gentoo.org/889330 Bug: https://bugs.gentoo.org/890777 Bug: https://bugs.gentoo.org/891391 Bug: https://bugs.gentoo.org/893638 Bug: https://bugs.gentoo.org/795825 Bug: https://bugs.gentoo.org/884869 Bug: https://bugs.gentoo.org/888585 Bug: https://bugs.gentoo.org/892651 Bug: https://bugs.gentoo.org/895526 Signed-off-by: Sam James <sam@gentoo.org> sys-apps/portage/Manifest | 1 + sys-apps/portage/portage-3.0.45.ebuild | 288 +++++++++++++++++++++++++++++++++ 2 files changed, 289 insertions(+) |