All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
	"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
	Edmar Wienskoski-RA8797 <Edmar@freescale.com>,
	Alan Modra <amodra@bigpond.net.au>,
	bug-binutils@gnu.org
Subject: Re: binutils 2.19 issue with kernel link
Date: Wed, 8 Jul 2009 22:52:59 -0500	[thread overview]
Message-ID: <AB02ECF3-9C72-436B-A946-CBCCD3859762@kernel.crashing.org> (raw)
In-Reply-To: <E6EB8DA7-8B38-4C97-BE3C-4649DFA295C8@kernel.crashing.org>


On Jul 8, 2009, at 10:39 PM, Kumar Gala wrote:

>
> On Jul 8, 2009, at 6:39 PM, Alan Modra wrote:
>
>> On Wed, Jul 08, 2009 at 05:41:39PM -0500, Kumar Gala wrote:
>>> If we modify the linker script:
>>>
>>>     _end2 = .;
>>>     _end3 = ALIGN(4096);
>>>     _end4 = ALIGN(PAGE_SIZE);
>>>     . = ALIGN(PAGE_SIZE);
>>>     _end = . ;
>>>     PROVIDE32 (end = .);
>>>
>>> and the result is:
>>>
>>> 00001000 A _end
>>> c067f678 A _end2
>>> c0680000 A _end3
>>> c0680000 A _end4
>>
>> Possibly some section with a zero vma is being placed before _end.
>> Generate a link map to see if this is so.
>
> Playing with this further I think its related to the -me500 option  
> we pass and thus wondering if its something with the APU section  
> handling.  If I hack the kernel up a little and pass -m440 instead  
> things seem to be ok.

To further verify this if I switch the -me500 to -mspe and build  
things seem to be ok.  This further points at some APU section related  
bug.

- k

  reply	other threads:[~2009-07-09  3:55 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 [this message]
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
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=AB02ECF3-9C72-436B-A946-CBCCD3859762@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=Edmar@freescale.com \
    --cc=amodra@bigpond.net.au \
    --cc=bug-binutils@gnu.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.