Hide Forgot
Clone of #1724130, created for the gcc component. Description of problem: Arm has introduced a vector PCS for SVE and Advanced SIMD. This showed a problem with lazy binding on SVE vector PCS while testing the qemu implementation of SVE primarily to do with saving and restoring the additional callee saved register state in the new vector PCS when lazily resolving SVE functions. The draft text for fixing the ABI for this is at https://sourceware.org/ml/libc-alpha/2019-05/msg00501.html It requires the marking of vector functions in the symbol table so the dynamic linker can bind them early. For this the symbol marking has to be propagated from the compiler to the final dynamic linked binary. Running an executable with vector pcs turned on for SVE. Note that such binaries could be generated by other commercial toolchains as well. This has been fixed by a series of patches for gcc binutils and glibc. These need to be backported on systems that run on SVE hardware to support binaries with extern SVE calls and to support compiling code with SVE or AdvSIMD vector calls. Without the glibc backport, the dynamic linker clobbers SVE call argument registers in the lazy binding entry code when the function is first called. So binaries with extern SVE calls will misbehave at runtime. Without the binutils backport, the bfd linker silently drops symbol markings at link time, creating broken binaries that misbehave even with an updated glibc. Without the binutils backport, the assembler fails to assemble code with SVE or AdvSIMD calls because it does not understand the new .variant_pcs directive. Without the gcc backport, gcc-9 emits AdvSIMD vector calls without marking them with .variant_pcs and thus they won't follow the new ABI. This is unlikely to cause runtime problems now as AdvSIMD registers are unlikely to be corrupted by the dynamic linker, but the marking is an ABI requirement and will be necessary to support LD_AUDIT or arbitrary ifunc resolvers for AdvSIMD vector calls among other features. We plan to backport the patches below to gcc-9, binutils-2.32 and several glibc release branches. patches: gcc: commit 779640c76d37b32f4d8a7b97637ed9e345d750b4 Commit: nsz <nsz@138bc75d-0d04-0410-961f-82ee72b054a4> CommitDate: 2019-06-03 13:50:53 +0000 aarch64: emit .variant_pcs for aarch64_vector_pcs symbol references git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@271869 138bc75d-0d04-0410-961f-82ee72b054a4 commit d403a7711c2cf9a7a4892d76b875a1c99a690f89 Commit: nsz <nsz@138bc75d-0d04-0410-961f-82ee72b054a4> CommitDate: 2019-06-04 16:16:52 +0000 aarch64: fix asm visibility for extern symbols git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@271913 138bc75d-0d04-0410-961f-82ee72b054a4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:1683