From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Introduce a new linker flag LDFLAGS_FINAL
Date: Sat, 05 Feb 2011 09:56:25 +1100 [thread overview]
Message-ID: <4D4C8419.3080103@gmail.com> (raw)
In-Reply-To: <20110201135136.0817fe5a@udp111988uds.am.freescale.net>
On 02/02/11 06:51, Scott Wood wrote:
> On Tue, 1 Feb 2011 20:32:29 +0100
> Wolfgang Denk <wd@denx.de> wrote:
>
>> Dear Scott Wood,
>>
>> In message <20110201102446.23b4a2e9@udp111988uds.am.freescale.net> you wrote:
>>>
>>> Prior to the introduction of LDFLAGS_u-boot, was LDFLAGS not what was
>>> used? So before, anything that board/cpu code adds directly to LDFLAGS
>>> (maybe they're supposed to use PLATFORM_LDFLAGS, but not all do) was
>>> used in the final link. After 8aba9dc, only things in
>>> PLATFORM_LDFLAGS plus -Bstatic and -T are used in the final link.
>>
>> And this is correct for all boards?
>
> By "this" do you mean the switch to PLATFORM_LDFLAGS in 8aba9dc, or the
> switch back to LDFLAGS? It's not obvious to me that the dropping of
> board/cpu modifications to LDFLAGS except during partial link was an
> intentional change, or a correct one for all boards.
>
> The only case I see where it makes any difference at all is arch/i386,
> which does LDFLAGS += --cref. From the description of --cref in the
> linker manual, it probably actually belongs in LDFLAGS_FINAL, though
> I'm not sure if it's harmless to include it in partial link or not.
> Currently, with 8aba9dc, it's included *only* in partial link.
>
> It's also not clear to me what this option has to do with i386... it
> looks like an arch-neutral debugging feature that doesn't affect the
> actual u-boot image at all (the output goes into the map file).
--cref can be dropped from x86 - I really should send a patch to rename
i386 to x86 ;)
Since x86 is currently a very simple platform to maintain (one CPU, one
board) and I have been dealing with breakages do to non x86 cleanups for a
while, I have no problem with tweaking the x86 linker options to be more
arch neutral.
Regards,
Graeme
next prev parent reply other threads:[~2011-02-04 22:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 18:32 [U-Boot] [PATCH] Introduce a new linker flag LDFLAGS_FINAL Haiying.Wang at freescale.com
2011-01-31 19:33 ` Wolfgang Denk
2011-01-31 19:55 ` Scott Wood
2011-02-01 7:34 ` Wolfgang Denk
2011-02-01 14:59 ` Haiying Wang
2011-02-01 16:24 ` Scott Wood
2011-02-01 19:32 ` Wolfgang Denk
2011-02-01 19:51 ` Scott Wood
2011-02-01 20:20 ` Wolfgang Denk
2011-02-01 20:40 ` Scott Wood
2011-02-04 15:52 ` Haiying Wang
2011-02-15 9:02 ` Mike Frysinger
2011-02-16 0:51 ` Scott Wood
2011-02-17 5:01 ` Mike Frysinger
2011-02-04 22:56 ` Graeme Russ [this message]
2011-01-31 20:14 ` Haiying Wang
2011-01-31 20:30 ` Wolfgang Denk
[not found] ` <1297878184.1977.18.camel@haiying-laptop>
2011-02-16 18:29 ` Wolfgang Denk
2011-02-16 18:40 ` Haiying Wang
2011-02-16 18:58 ` Wolfgang Denk
2011-02-17 5:37 ` Mike Frysinger
2011-02-17 8:33 ` Wolfgang Denk
2011-02-17 19:28 ` Haiying Wang
2011-02-17 20:38 ` Haiying Wang
2011-02-22 19:39 ` Wolfgang Denk
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=4D4C8419.3080103@gmail.com \
--to=graeme.russ@gmail.com \
--cc=u-boot@lists.denx.de \
/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