From: Alan Modra <amodra@bigpond.net.au>
To: binutils@sources.redhat.com
Subject: Re: elf_backend_hide_symbol
Date: Mon, 04 Mar 2002 21:24:00 -0000 [thread overview]
Message-ID: <20020305052438.GT1090@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <20020305051742.GS1090@bubble.sa.bigpond.net.au>
On Tue, Mar 05, 2002 at 03:47:42PM +1030, Alan Modra wrote:
> > * elflink.h (elf_bfd_final_link): Call elf_link_output_extsym
> > to output forced local syms for non-shared link.
> > (elf_link_output_extsym): Tweak condition for calling backend
> > adjust_dynamic_symbol so that previous behaviour is kept.
This hack can go now too.
bfd/ChangeLog
* elf32-hppa.c (clobber_millicode_symbols): Remove hack to keep
symbols that have been forced local.
Index: bfd/elf32-hppa.c
===================================================================
RCS file: /cvs/src/src/bfd/elf32-hppa.c,v
retrieving revision 1.72
diff -u -p -r1.72 elf32-hppa.c
--- elf32-hppa.c 2002/02/19 12:40:24 1.72
+++ elf32-hppa.c 2002/03/05 05:22:52
@@ -2217,10 +2217,6 @@ clobber_millicode_symbols (h, info)
&& (h->elf_link_hash_flags & ELF_LINK_FORCED_LOCAL) == 0)
{
elf32_hppa_hide_symbol (info, h, true);
-
- /* ?!? We only want to remove these from the dynamic symbol table.
- Therefore we do not leave ELF_LINK_FORCED_LOCAL set. */
- h->elf_link_hash_flags &= ~ELF_LINK_FORCED_LOCAL;
}
return true;
}
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2002-03-05 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 17:11 elf_backend_hide_symbol Alan Modra
2002-03-04 21:17 ` elf_backend_hide_symbol Alan Modra
2002-03-04 21:24 ` Alan Modra [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-21 3:02 elf_backend_hide_symbol Alan Modra
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=20020305052438.GT1090@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.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).