public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/5] spl: don't mark __u_boot_cmd* as undefined
Date: Mon, 6 Aug 2012 08:30:56 -0700	[thread overview]
Message-ID: <501FE330.4090603@ti.com> (raw)
In-Reply-To: <CAA3CPjUVNhmYT4JbTz_WVb6TfqGy=SoQqy0u30yk+C_Pg0Qkhg@mail.gmail.com>

On 08/06/2012 08:10 AM, Ilya Yanok wrote:
> Hi Tom,
> 
> On Mon, Aug 6, 2012 at 2:36 AM, Tom Rini <trini@ti.com
> <mailto:trini@ti.com>> wrote:
> 
>     On Sun, Aug 5, 2012 at 2:21 PM, Ilya Yanok
>     <ilya.yanok@cogentembedded.com
>     <mailto:ilya.yanok@cogentembedded.com>> wrote:
>     > __u_boot_cmd* symbols are not used in SPL so there is no need
>     > to tell the linker that they are undefined. With these symbols
>     > marked as undefined linker fails to garbage collect some unused
>     > functions and even fails to build the resulting image.
> 
>     I don't like this because it causes SPL to bloat when the commands
>     aren't also removed from the build.  But I assume a number of commands
> 
> 
> Nah. As far as I understand it,  UNDEF_SYM stuff is there to protect
> commands from being purged by linker garbage collector. This is needed
> for main U-Boot as commands are referenced inderectly.
> I seems to me that this stuff was just copy-pasted into SPL Makefile. As
> far as we don't need commands in SPL we don't care about them being
> garbage collected (well, actually we want them to be collected). So it
> has nothing to do about bloating, actually SPL image is smaller with
> this patch applied.

What toolchain are you using?  In my tests they have not been collected.

-- 
Tom

  reply	other threads:[~2012-08-06 15:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05 21:21 [U-Boot] [PATCH v4 0/5] OMAP: SPL networking support Ilya Yanok
2012-08-05 21:21 ` [U-Boot] [PATCH v4 1/5] net/bootp: add VCI support for BOOTP also Ilya Yanok
2012-08-10 17:57   ` Ilya Yanok
2012-08-29 21:01   ` Joe Hershberger
2012-08-05 21:21 ` [U-Boot] [PATCH v4 2/5] spl: don't mark __u_boot_cmd* as undefined Ilya Yanok
2012-08-05 22:36   ` Tom Rini
2012-08-06 15:10     ` Ilya Yanok
2012-08-06 15:30       ` Tom Rini [this message]
2012-08-06 15:31         ` Ilya Yanok
2012-08-06 17:10           ` Tom Rini
2012-08-06 19:15             ` Ilya Yanok
2012-08-06 20:52               ` Tom Rini
2012-08-06 21:11                 ` Ilya Yanok
2012-08-07  8:12                   ` Ilya Yanok
2012-08-05 21:21 ` [U-Boot] [PATCH v4 3/5] OMAP: spl: call timer_inti() from SPL Ilya Yanok
2012-08-05 22:35   ` Tom Rini
2012-08-06 15:02     ` Ilya Yanok
2012-08-06 15:11       ` Tom Rini
2012-08-06 18:49   ` [U-Boot] [PATCH] am33xx: Remove redundant timer config Tom Rini
2012-08-05 21:21 ` [U-Boot] [PATCH v4 4/5] OMAP: networking support for SPL Ilya Yanok
2012-08-07  8:07   ` [U-Boot] [PATCH v5 " Ilya Yanok
2012-08-29 21:25     ` Joe Hershberger
2012-08-29 22:28       ` Tom Rini
2012-09-17  9:55       ` Ilya Yanok
2012-09-17 17:04         ` Tom Rini
2012-09-17 17:54           ` Ilya Yanok
2012-09-17 18:07             ` Tom Rini
2012-09-17 18:10               ` Ilya Yanok
2012-09-17 18:16                 ` Ilya Yanok
2012-09-17 18:19                 ` Tom Rini
2012-09-17 18:36         ` Ilya Yanok
2012-08-05 21:21 ` [U-Boot] [PATCH v4 5/5] am335x_evm: enable networking in SPL Ilya Yanok

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=501FE330.4090603@ti.com \
    --to=trini@ti.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