From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v2] x86-64: Add -z mark-plt and -z nomark-plt
Date: Thu, 28 Sep 2023 16:54:48 +0200 [thread overview]
Message-ID: <3461f66b-9152-baa8-9345-76a78ee1ec29@suse.com> (raw)
In-Reply-To: <CAMe9rOoB5UGCk1k95DEENZObWCxU7nzigeiXcXiFVb9kjRNfMA@mail.gmail.com>
On 28.09.2023 16:52, H.J. Lu wrote:
> On Wed, Sep 27, 2023 at 11:07 PM Jan Beulich <jbeulich@suse.com> wrote:
>>
>> On 27.09.2023 19:19, H.J. Lu via Binutils wrote:
>>> --- a/ld/ld.texi
>>> +++ b/ld/ld.texi
>>> @@ -1475,6 +1475,11 @@ Specify that the object's filters be processed immediately at runtime.
>>> @item max-page-size=@var{value}
>>> Set the maximum memory page size supported to @var{value}.
>>>
>>> +@item mark-plt
>>> +@itemx nomark-plt
>>> +Mark PLT entries with dynamic tags, DT_X86_64_PLT, DT_X86_64_PLTSZ and
>>> +DT_X86_64_PLTENT. Supported for x86_64.
>>
>> Hmm, you use backwards compatibility issues as justification for not having
>> a configure time way to default the new behavior to enabled, and then you
>> don't mention the backwards compatibility aspect here?
>>
>
> How about this:
>
> @item mark-plt
> @itemx nomark-plt
> Mark PLT entries with dynamic tags, DT_X86_64_PLT, DT_X86_64_PLTSZ and
> DT_X86_64_PLTENT. Since this option stores a non-zero value in the
> r_addend field of R_X86_64_JUMP_SLOT relocations, the resulting
> executables and shared libraries are incompatible with dynamic linkers,
> such as those in older versions of glibc without the change to ignore
> r_addend in R_X86_64_GLOB_DAT and R_X86_64_JUMP_SLOT relocations, which
> don't ignore the r_addend field of R_X86_64_JUMP_SLOT relocations.
> Supported for x86_64.
Reads okay to me, thanks.
Jan
prev parent reply other threads:[~2023-09-28 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 17:19 H.J. Lu
2023-09-28 6:00 ` Jan Beulich
2023-09-28 6:07 ` Jan Beulich
2023-09-28 7:02 ` Fangrui Song
2023-09-28 14:52 ` H.J. Lu
2023-09-28 14:54 ` Jan Beulich [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=3461f66b-9152-baa8-9345-76a78ee1ec29@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).