All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edmar Wienskoski-RA8797 <edmar@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
	"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
	Alan Modra <amodra@bigpond.net.au>,
	bug-binutils@gnu.org
Subject: Re: binutils 2.19 issue with kernel link
Date: Thu, 09 Jul 2009 14:31:53 -0500	[thread overview]
Message-ID: <4A5645A9.3080003@freescale.com> (raw)
In-Reply-To: <4B3B917C-C8B0-416B-888D-13E6C0645BF8@kernel.crashing.org>

Kumar Gala wrote:
>
> On Jul 8, 2009, at 11:40 PM, Alan Modra wrote:
>
>> On Wed, Jul 08, 2009 at 10:52:59PM -0500, Kumar Gala wrote:
>>> 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.
>>
>> Like omitting .PPC.EMB.apuinfo from your kernel link script?  See the
>> ld info doc on orphan sections.
>
> Ok, not terribly enlightening, but why would .PPC.EMB.apuinfo sections 
> be different than something like .debug sections which we also dont 
> list in the linker script.
>
> - k
>
Alan,

I understand your arguments, but there is something inconsistent about this.
If I change the script to be:
        _end3 = . ;
        . = _end3;
        . = ALIGN(PAGE_SIZE);
        _end = . ;
        PROVIDE32 (end = .);
}
The result is corrected:
c067f678 A _end3
c0680000 A _end

Why the apuinfo section with zero VMA sometimes interfere with "." and 
sometimes not ?

Edmar

  reply	other threads:[~2009-07-09 19:32 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 [this message]
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=4A5645A9.3080003@freescale.com \
    --to=edmar@freescale.com \
    --cc=amodra@bigpond.net.au \
    --cc=bug-binutils@gnu.org \
    --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.