From: Alan Modra <amodra@bigpond.net.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
bug-binutils@gnu.org,
Edmar Wienskoski-RA8797 <edmar@freescale.com>
Subject: Re: binutils 2.19 issue with kernel link
Date: Sat, 11 Jul 2009 09:35:03 +0930 [thread overview]
Message-ID: <20090711000503.GO3181@bubble.grove.modra.org> (raw)
In-Reply-To: <4F69F333-8BCA-4BB8-A5C1-4B25EA5D1287@kernel.crashing.org>
On Fri, Jul 10, 2009 at 10:27:26AM -0500, Kumar Gala wrote:
> binutils-2.19 _end is what we expect
> binutils-2.19.1 _end is what we expect
> binutils-2.19.50.0.1 _end is what we expect
> binutils-2.19.51.0.1 _end is 00001000
>
> From the release notes:
>
> binutils-2.19.50.0.1 is based on CVS binutils 2008 1007
> binutils-2.19.51.0.1 is based on CVS binutils 2009 0106
Yes, I already have good reason to suspect this patch
2008-10-22 Alan Modra <amodra@bigpond.net.au>
* ldlang.c (lang_output_section_find_by_flags): Handle non-alloc
sections.
* emultempl/elf32.em (enum orphan_save_index): Add orphan_nonalloc.
(hold): Likewise.
(gld${EMULATION_NAME}_place_orphan): Handle non-alloc orphans.
causes the change in linker behaviour. Did you try the patch I posted?
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2009-07-11 0:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 22:41 binutils 2.19 issue with kernel link Kumar Gala
2009-07-08 23:39 ` Alan Modra
2009-07-09 2:40 ` Kumar Gala
2009-07-09 3:39 ` Kumar Gala
2009-07-09 3:52 ` Kumar Gala
2009-07-09 4:40 ` Alan Modra
2009-07-09 15:22 ` Kumar Gala
2009-07-09 19:31 ` Edmar Wienskoski-RA8797
2009-07-10 4:11 ` Alan Modra
2009-07-10 15:34 ` Kumar Gala
2009-07-10 4:15 ` Alan Modra
2009-07-10 14:37 ` Kumar Gala
2009-07-10 15:27 ` Kumar Gala
2009-07-11 0:05 ` Alan Modra [this message]
2009-07-11 0:08 ` Alan Modra
2009-07-09 16:39 ` Dale Farnsworth
2009-07-09 18:14 ` Kumar Gala
2009-07-09 19:06 ` Dale Farnsworth
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=20090711000503.GO3181@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=bug-binutils@gnu.org \
--cc=edmar@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.