From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Florian Weimer <fweimer@redhat.com>,
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: Fri, 17 Aug 2018 08:10:15 -0700 [thread overview]
Message-ID: <CAMe9rOq3S191Oy9LNGquns427gsP_HrhY_U2e=mynNc9o7Rq9Q@mail.gmail.com> (raw)
In-Reply-To: <20180817064146.GD8094@wildebeest.org>
On Thu, Aug 16, 2018 at 11:41 PM, Mark Wielaard <mark@klomp.org> wrote:
> On Fri, Aug 17, 2018 at 08:20:53AM +0200, Florian Weimer wrote:
>> > Having a mix of 4-byte words and 8-byte words ELF Notes
>> > in the same ELF file seems unnecessarily confusing and
>> > introduces extra segments and sections.
>>
>> There are no 8-byte word ELF notes on GNU systems, that's an HP-UX feature.
>> The new 8-byte-aligned notes still have a four-byte header.
>
> Yes, you are right, HP-UX follows gabi and has 64-bit word notes,
> with 8-byte alignment. I meant the different padding used with GNU
> style 32-bit word ELF notes to get different alignment styles which
> is confusing and none compliant to any standard.
>
>> But like you, I don't yet see the value of the 8-byte alignment. We could
>> decide that the current gold behavior is valid, fix glibc, and move on.
>
> Right. gold seems to produce normal GNU abi ELF Notes, which should
> be accepted as is.
>
NT_GNU_PROPERTY_TYPE_0 should stay to follow gABI.
--
H.J.
next prev parent reply other threads:[~2018-08-17 15:10 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
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 [this message]
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='CAMe9rOq3S191Oy9LNGquns427gsP_HrhY_U2e=mynNc9o7Rq9Q@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.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).