From: Andreas Krebbel <krebbel@linux.ibm.com>
To: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>,
binutils@sourceware.org
Subject: Re: [PATCH] IBM zSystems: Fix offset relative to static TLS
Date: Tue, 10 Jan 2023 14:40:28 +0100 [thread overview]
Message-ID: <44139fd1-5f40-ff9a-828d-df4e41623e7a@linux.ibm.com> (raw)
In-Reply-To: <20230110133534.5295-1-stefansf@linux.ibm.com>
On 1/10/23 14:35, Stefan Schulze Frielinghaus wrote:
> For local exec TLS relocations of the form foo@NTPOFF+x the addend was
> ignored.
>
> Build and tested on s390x. Ok for mainline and branches 2.{39,40}?
>
> bfd/ChangeLog:
>
> * elf32-s390.c (elf_s390_relocate_section): Honor addend for
> R_390_TLS_LE32.
> * elf64-s390.c (elf_s390_relocate_section): Honor addend for
> R_390_TLS_LE64.
>
> ld/ChangeLog:
>
> * testsuite/ld-s390/reloctlsle-1.d: New test.
> * testsuite/ld-s390/reloctlsle-1.s: New test.
Ok for mainline and release branches. Thanks!
Andreas
prev parent reply other threads:[~2023-01-10 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 13:35 Stefan Schulze Frielinghaus
2023-01-10 13:40 ` Andreas Krebbel [this message]
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=44139fd1-5f40-ff9a-828d-df4e41623e7a@linux.ibm.com \
--to=krebbel@linux.ibm.com \
--cc=binutils@sourceware.org \
--cc=stefansf@linux.ibm.com \
/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).