From: Scott Wood <scottwood@freescale.com>
To: Sanal Kumar V K <sanalvk@centillium.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Running a section of code from internal memory
Date: Mon, 12 May 2008 10:56:33 -0500 [thread overview]
Message-ID: <482868B1.9090005@freescale.com> (raw)
In-Reply-To: <48285544.7040908@centillium.com>
Sanal Kumar V K wrote:
> Now if I make the following entry in the linker script,
> /* define L2 scratch here */
> . = 0x9FC16800;
> .l2_scratch : { *(.l2_scratch) }
>
> it says "collect2: ld returned 1 exit status".
I'm guessing there was an earlier error message printed by ld?
You probably located the L2 section too far away from the main section,
and it's trying to do short branches or other limited relocations.
-Scott
prev parent reply other threads:[~2008-05-12 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 11:36 Running a section of code from internal memory Sanal Kumar V K
2008-05-08 12:45 ` Marco Stornelli
2008-05-08 15:33 ` Scott Wood
2008-05-12 14:33 ` Sanal Kumar V K
2008-05-12 15:56 ` Scott Wood [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=482868B1.9090005@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sanalvk@centillium.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 NNTP newsgroup(s).