From: Alan Modra <amodra@gmail.com>
To: Will Newton <will.newton@linaro.org>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: 32-bit PowerPC sdata linker problem
Date: Wed, 18 Jun 2014 00:29:00 -0000 [thread overview]
Message-ID: <20140618002900.GM3462@bubble.grove.modra.org> (raw)
In-Reply-To: <CANu=DmjAnLsxZ2sHN86xVxN5+2swirScH5iYDwfUrwRaZRN_bg@mail.gmail.com>
On Mon, Jun 16, 2014 at 03:11:12PM +0100, Will Newton wrote:
> On 16 June 2014 15:09, Will Newton <will.newton@linaro.org> wrote:
> > On 16 June 2014 14:07, Alan Modra <amodra@gmail.com> wrote:
> >> On Mon, Jun 16, 2014 at 12:21:23PM +0100, Will Newton wrote:
> >>> PROVIDE_HIDDEN (__rel_iplt_start = .);
> >>> *(.rel.iplt)
> >>> PROVIDE_HIDDEN (__rel_iplt_end = .);
> >>> PROVIDE_HIDDEN (__rela_iplt_start = .);
> >>> PROVIDE_HIDDEN (__rela_iplt_end = .);
> >>
> >> This should fix it. Committed.
> >>
> >> * scripttempl/elf.sc: Edit out __rela_iplt symbol assignments from
> >> .rel sections, and __rel_iplt from .rela sections.
> >> * scripttempl/nds32elf.sc: Likewise.
> >> * Makefile.am (ends32*.c) Depend on nds32elf.sc.
> >> * Makefile.in: Regenerate.
> >
> > Yes, this fixes the problem for me. Thanks!
>
> Would it be possible to apply the fix to the stable branch too?
Done. I'm also going to commit the following to 2.24.
PR 17047
* ldlang.c (lang_finish): Don't free linker hash table.
diff --git a/ld/ldlang.c b/ld/ldlang.c
index ba7f493..9121aa2 100644
--- a/ld/ldlang.c
+++ b/ld/ldlang.c
@@ -1238,7 +1238,14 @@ lang_init (void)
void
lang_finish (void)
{
+ /* Some targets require access to the linker hash table during the
+ _bfd_write_contents call in bfd_close, so it can't be freed
+ before bfd_close. It can't be freed after bfd_close either,
+ since bfd_alloc memory holding side data structures disappears
+ (PR17047). So don't free it.
+
bfd_link_hash_table_free (link_info.output_bfd, link_info.hash);
+ */
bfd_hash_table_free (&lang_definedness_table);
output_section_statement_table_free ();
}
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2014-06-18 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53918356.3040102@embedded-brains.de>
2014-06-06 10:54 ` Alan Modra
2014-06-06 11:23 ` Sebastian Huber
2014-06-06 11:31 ` Sebastian Huber
2014-06-06 12:15 ` Alan Modra
2014-06-06 12:49 ` Sebastian Huber
[not found] ` <20140606130559.GK5592@bubble.grove.modra.org>
[not found] ` <5391C0E8.7010409@embedded-brains.de>
[not found] ` <20140606134915.GL5592@bubble.grove.modra.org>
[not found] ` <5391CCFB.5060206@embedded-brains.de>
2014-06-07 12:34 ` Alan Modra
2014-06-10 6:28 ` Sebastian Huber
2014-06-06 12:17 ` Alan Modra
2014-06-07 12:47 ` Alan Modra
2014-06-16 11:21 ` Will Newton
2014-06-16 13:07 ` Alan Modra
2014-06-16 14:10 ` Will Newton
2014-06-16 14:11 ` Will Newton
2014-06-18 0:29 ` Alan Modra [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=20140618002900.GM3462@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=will.newton@linaro.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).