From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: x86-64-abi <x86-64-abi@googlegroups.com>,
Binutils <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: PT_NOTE alignment, NT_GNU_PROPERTY_TYPE_0, glibc and gold
Date: Thu, 16 Aug 2018 16:01:23 +0200 [thread overview]
Message-ID: <8375685a-888d-7610-3b93-0d50bca32698@redhat.com> (raw)
In-Reply-To: <CAMe9rOo2Qw7UV8ApqtN79=L47wtWGnvzakfFveQmoUyjK=jpew@mail.gmail.com>
On 08/16/2018 03:39 PM, H.J. Lu wrote:
> On Thu, Aug 16, 2018 at 6:31 AM, Florian Weimer <fweimer@redhat.com> wrote:
>> On 08/16/2018 03:19 PM, H.J. Lu wrote:
>>>
>>> On Thu, Aug 16, 2018 at 6:00 AM, Florian Weimer <fweimer@redhat.com>
>>> wrote:
>>>>
>>>> On 08/07/2018 10:41 PM, H.J. Lu wrote:
>>>>>
>>>>>
>>>>> The .note.gnu.property section with NT_GNU_PROPERTY_TYPE_0 has been
>>>>> added to Linux Extensions to gABI:
>>>>>
>>>>> https://github.com/hjl-tools/linux-abi
>>>>>
>>>>> GNU_PROPERTY_X86_ISA_1_USED and GNU_PROPERTY_X86_ISA_1_NEEDED are
>>>>> processor-specific program property types for i386 and x86-64.
>>>>
>>>>
>>>>
>>>> The specification is incomplete as far as alignment matters are
>>>> concerned.
>>>
>>>
>>> https://github.com/hjl-tools/linux-abi/wiki/linux-abi-draft.pdf
>>>
>>> has
>>>
>>> 2.1.7 Alignment of Note Sections
>>>
>>> All entries in a PT_NOTE segment have the same alignment which equals to
>>> the
>>> p_align field in program header.
>>> According to gABI, each note entry should be aligned to 4 bytes in 32-bit
>>> objects or 8 bytes in 64-bit objects. But .note.ABI-tag section (see
>>> Section 2.1.6) and .note.gnu.build-id section (see Section 2.1.4) are
>>> aligned
>>> to 4 bytes in both 32-bit and 64-bit objects. Note parser should use
>>> p_align for
>>> note alignment, instead of assuming alignment based on ELF file class.
>>
>>
>> This is still ambiguous, particularly based on your comments below.
>
> https://github.com/hjl-tools/linux-abi/wiki/linux-abi-draft.pdf
>
> conforms to gABI unless stated otherwise.
I still think there is ambiguity.
> I was wrong. We need 2 NOTE segments one fore 8-byte alignment and
> one for 4-byte alignment.
If one needs to generate two segments, the ABI documents should say so.
Otherwise, linker implementors will assume that there are other ways to
implement this.
> glibc only discards 4-byte aligned NT_GNU_PROPERTY_TYPE_0 note
> since NT_GNU_PROPERTY_TYPE_0 note follows gABI. If gold
> generates 4 byte alignment, it is a gold bug.
See above. I don't have a strong opinion how we make gold and glibc
interoperate, but if gold is wrong, the ABI documents should be made
more precise.
Thanks,
Florian
next prev parent reply other threads:[~2018-08-16 14:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMe9rOrrayKnc_cPm4SmnDnUGLbBUmOYMBTMOM8KLAHVmb=rUQ@mail.gmail.com>
2018-08-16 13:00 ` PT_NOTE alignment, NT_GNU_PROPERTY_TYPE_0, glibc and gold (was: Re: [PATCH] Document GNU_PROPERTY_X86_ISA_1_[USED|NEEDED]) Florian Weimer
2018-08-16 13:19 ` H.J. Lu
2018-08-16 13:29 ` H.J. Lu
2018-08-16 13:31 ` PT_NOTE alignment, NT_GNU_PROPERTY_TYPE_0, glibc and gold Florian Weimer
2018-08-16 13:39 ` H.J. Lu
2018-08-16 14:01 ` Florian Weimer [this message]
2018-08-16 14:43 ` H.J. Lu
2018-08-16 14:21 ` Florian Weimer
2018-08-16 17:46 ` H.J. Lu
2018-08-16 19:16 ` Mark Wielaard
2018-08-16 19:36 ` H.J. Lu
2018-08-17 6:04 ` Mark Wielaard
2018-08-17 6:20 ` Florian Weimer
2018-08-17 6:41 ` Mark Wielaard
2018-08-17 15:10 ` H.J. Lu
2018-08-17 21:05 ` Mark Wielaard
2018-08-21 23:02 ` Cary Coutant
2018-08-22 9:39 ` Florian Weimer
2018-08-22 10:08 ` Mark Wielaard
2018-08-22 23:36 ` Cary Coutant
2018-08-24 18:39 ` Florian Weimer
2018-08-23 14:41 ` Michael Matz
2018-08-23 14:43 ` Florian Weimer
2018-08-17 15:13 ` H.J. Lu
2018-09-19 19:22 ` Florian Weimer
2018-09-21 12:55 ` Michael Matz
2018-09-21 13:04 ` Florian Weimer
2018-09-26 17:39 ` Cary Coutant
2018-09-26 18:36 ` H.J. Lu
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8375685a-888d-7610-3b93-0d50bca32698@redhat.com \
--to=fweimer@redhat.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=x86-64-abi@googlegroups.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).