public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/26798] aarch64: variant PCS symbols may be incorrectly lazy bound
Date: Wed, 04 Nov 2020 12:37:05 +0000 [thread overview]
Message-ID: <bug-26798-131-KOl5cByOJ9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26798-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26798
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.32/master branch has been updated by Szabolcs Nagy
<nsz@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=70ee5e8b573f76745760dd6b75f705590fc1923a
commit 70ee5e8b573f76745760dd6b75f705590fc1923a
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Oct 22 17:55:01 2020 +0100
aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
The variant PCS support was ineffective because in the common case
linkmap->l_mach.plt == 0 but then the symbol table flags were ignored
and normal lazy binding was used instead of resolving the relocs early.
(This was a misunderstanding about how GOT[1] is setup by the linker.)
In practice this mainly affects SVE calls when the vector length is
more than 128 bits, then the top bits of the argument registers get
clobbered during lazy binding.
Fixes bug 26798.
(cherry picked from commit 558251bd8785760ad40fcbfeaaee5d27fa5b0fe4)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-04 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 9:23 [Bug dynamic-link/26798] New: " nsz at gcc dot gnu.org
2020-10-29 8:42 ` [Bug dynamic-link/26798] " nsz at gcc dot gnu.org
2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
2020-11-02 9:40 ` cvs-commit at gcc dot gnu.org
2020-11-02 10:45 ` fweimer at redhat dot com
2020-11-02 13:31 ` nsz at gcc dot gnu.org
2020-11-02 13:33 ` nsz at gcc dot gnu.org
2020-11-04 12:37 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-04 12:39 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:40 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:42 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:44 ` cvs-commit at gcc dot gnu.org
2020-11-04 12:45 ` cvs-commit at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-26798-131-KOl5cByOJ9@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).