From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24251] Allocatable section after non-allocatable ones
Date: Fri, 25 Sep 2020 08:03:56 +0000 [thread overview]
Message-ID: <bug-24251-11298-BYwfspmqTH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24251-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24251
--- Comment #17 from Jakub Jelinek <jakub at redhat dot com> ---
ELF doesn't have many requirements and the consumers just choose what to
ignore. The kernel loader, glibc etc. will reject many "valid" kinds of ELF
too, they just expect sane linkers to generate something that makes sense. And
the same is with dwz (and used to be e.g. with prelink), if the
linker/assembler produces garbage, then it is better to fix those. When
binutils at some point produced also section orderings that dwz/prelink didn't
like, we've fixed binutils not to do that.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-25 8:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/24251] New: " vries at gcc dot gnu.org
2019-01-01 0:00 ` [Bug default/24251] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2020-09-06 19:28 ` jan.kratochvil at redhat dot com
2020-09-07 7:53 ` mark at klomp dot org
2020-09-07 8:01 ` jan.kratochvil at redhat dot com
2020-09-08 13:27 ` vries at gcc dot gnu.org
2020-09-17 15:51 ` mark at klomp dot org
2020-09-24 22:18 ` mark at klomp dot org
2020-09-25 7:56 ` jan.kratochvil at redhat dot com
2020-09-25 8:03 ` jakub at redhat dot com [this message]
2020-09-25 9:44 ` mark at klomp dot org
2020-09-25 9:52 ` jan.kratochvil at redhat dot com
2020-09-25 18:49 ` mark at klomp dot org
2021-02-13 23:05 ` mark at klomp dot org
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=bug-24251-11298-BYwfspmqTH@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@sourceware.org \
/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).