From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Jan Beulich <jbeulich@suse.com>
Cc: Chenghua Xu <paul.hua.gm@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: non-conformant ELF symbol table on MIPS?
Date: Fri, 28 Jul 2023 07:56:39 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2307280739510.10240@angie.orcam.me.uk> (raw)
In-Reply-To: <5a410132-b62f-b932-cb00-ee6ad0a3a99b@suse.com>
On Fri, 28 Jul 2023, Jan Beulich wrote:
> > There are two kinds of MIPS targets, ones that use the older IRIX symbol
> > sorting rules and ones that use the newer "traditional" symbol sorting
> > rules. The IRIX symbol sorting rules mandate that section symbols precede
> > all other symbols, see e.g. bfd/elf32-mips.c:mips_elf_sym_is_global.
>
> Along the lines of my reply to Ian: This still doesn't explain the
> behavior I observe. What you say is required could still be met without
> violating ELF rules.
Yes, we could put section symbols first, then local ones, then external
ones, and it was discussed many years ago, but it would require rather a
heavy overhaul of generic parts of BFD. Someone would have to do it just
to handle a corner case, so it was concluded that it wouldn't be the best
use of time, which would better be spent on something more important.
Maciej
prev parent reply other threads:[~2023-07-28 6:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:27 Jan Beulich
2023-07-27 19:04 ` Ian Lance Taylor
2023-07-27 19:39 ` Maciej W. Rozycki
2023-07-28 6:16 ` Jan Beulich
2023-07-28 17:11 ` Ian Lance Taylor
2023-07-28 23:58 ` Alan Modra
2023-07-27 19:28 ` Maciej W. Rozycki
2023-07-28 6:13 ` Jan Beulich
2023-07-28 7:18 ` Jan Beulich
2023-07-28 6:18 ` Jan Beulich
2023-07-28 6:56 ` Maciej W. Rozycki [this message]
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=alpine.DEB.2.21.2307280739510.10240@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=paul.hua.gm@gmail.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).