From: Florian Weimer <fweimer@redhat.com>
To: Michael Matz <matz@suse.de>
Cc: x86-64-abi@googlegroups.com, Binutils <binutils@sourceware.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>,
Mark Wielaard <mark@klomp.org>,
Cary Coutant <ccoutant@gmail.com>,
Nick Clifton <nickc@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: Re: PT_NOTE alignment, NT_GNU_PROPERTY_TYPE_0, glibc and gold
Date: Fri, 21 Sep 2018 15:04:04 +0200 [thread overview]
Message-ID: <87worfdmt7.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1809211232400.7867@wotan.suse.de> (Michael Matz's message of "Fri, 21 Sep 2018 12:55:16 +0000 (UTC)")
* Michael Matz:
> (didn't take part in the side meeting, so sorry if this was discussed)
I don't think this came up.
> On Wed, 19 Sep 2018, Florian Weimer wrote:
>
>> Distributions have built binaries with 8-byte-aligned GNU property
>> notes.
>
> Which ones?
Fedora 29 and downstream.
> Thing is, there are also binaries (or there could be) that are currently
> "valid" that the align-8 approach makes invalid, so why say that's a
> problem for the align-4 approach, but not for the align-8 one?
The 4-byte-aligned GNU property notes are ignored by glibc even if they
are otherwise syntactically valid. So even if there is a hypothetical
distribution that is mostly built with binutils gold and thus has
4-byte-aligned GNU property notes, it would still not work as intended,
which makes me believe that such a distribution does not exist. 8-)
Thanks,
Florian
next prev parent reply other threads:[~2018-09-21 13:04 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
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 [this message]
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=87worfdmt7.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=ccoutant@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=matz@suse.de \
--cc=nickc@redhat.com \
--cc=szabolcs.nagy@arm.com \
--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).