From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Szabolcs Nagy <nsz@port70.net>, Jan Beulich <JBeulich@suse.com>,
Rich Felker <dalias@libc.org>, Binutils <binutils@sourceware.org>,
gnu-gabi@sourceware.org
Subject: Re: RFC: Add SHT_GNU_PHDRS
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <15841ff4-88dc-04b5-487c-478fcb2a66cf@redhat.com> (raw)
In-Reply-To: <CAMe9rOoCx4k4EMkB1kAqPuT6Y0mYN6RrOQ38FDf7fMmHgJDKJw@mail.gmail.com>
On 9/27/18 12:26 PM, H.J. Lu wrote:
> [hjl@gnu-cfl-1 ld]$ ../binutils/objcopy ./foo bar
> ../binutils/objcopy: bar: section .gnu.phdrs lma 0x400040 adjusted to 0x401040
What is it doing here? Why is it adjusting the lma? How odd.
> [hjl@gnu-cfl-1 ld]$
>
> I can fix objcopy. Other tools may also need adjustment.
Yes, this just looks like bugs.
* Unknown section types should not be adjusted or touched and minimally passed
through during a copy. We should not adjust them to the next PROGBITS section.
* Backports of the fix to active branches to enable distributions to easily
pickup the fixes.
... and keep moving forward with a proper fix (and consensus around it).
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-09-27 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 H.J. Lu
[not found] ` <CAORpzuOWtHeqBLEE+MMN4-TZyp6Z1r-MdmyNv7Zj-BhxMstr=g@mail.gmail.com>
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Jan Beulich
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Szabolcs Nagy
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Rich Felker
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` H.J. Lu
2018-01-01 0:00 ` Carlos O'Donell [this message]
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Michael Matz
2018-01-01 0:00 ` Florian Weimer
2018-01-01 0:00 ` Cary Coutant
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15841ff4-88dc-04b5-487c-478fcb2a66cf@redhat.com \
--to=carlos@redhat.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=dalias@libc.org \
--cc=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=nsz@port70.net \
/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).