From: "Maciej W. Rozycki" <macro@mips.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Simon Atanasyan <simon@atanasyan.com>, <binutils@sourceware.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH v4] BFD: Prevent writing the MIPS _gp_disp symbol into symbol tables
Date: Tue, 01 May 2018 11:54:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1805011247380.11756@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1804301935440.3035@digraph.polyomino.org.uk>
On Mon, 30 Apr 2018, Joseph Myers wrote:
> > Therefore I think we should selectively ignore it. What you write
> > implies we have no predefined way of doing that, and it looks to me like
> > we ought to define a way to feed `scripts/abilist.awk' a (carefully
> > selected) list of symbols to ignore in processing.
>
> But do we need such a list, or would just ignoring all absolute symbols
> suffice?
>
> At present, abilist.awk shows such symbols with a type of "A". Apart from
> symbol version names, _gp_disp seems to be the only such symbol. Is there
> any need to have the "A" lines for each symbol version in the abilist
> files?
I don't know. Perhaps someone else knows.
As I noted stripping the problematic symbol is IMO the best solution.
Using `$CC -print-prog-name=strip' to discover where the right `strip'
binary is should be a straightforward way to arrange that in a platform
`configure' fragment. Then we can dump `_gp_disp' from .abilist files.
Maciej
next prev parent reply other threads:[~2018-05-01 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180429065756.bvponxkyyqtmdrbg@debian64.galaxy.int>
[not found] ` <alpine.DEB.2.00.1804300946270.11756@tp.orcam.me.uk>
[not found] ` <alpine.DEB.2.20.1804301518320.17105@digraph.polyomino.org.uk>
2018-04-30 16:27 ` Maciej W. Rozycki
2018-04-30 19:38 ` Joseph Myers
2018-05-01 11:54 ` Maciej W. Rozycki [this message]
2018-05-01 14:40 ` Joseph Myers
2018-05-02 15:49 ` Maciej W. Rozycki
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.00.1805011247380.11756@tp.orcam.me.uk \
--to=macro@mips.com \
--cc=binutils@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=simon@atanasyan.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).