mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: socfpga: generate smaller images when multiple boards are selected
Date: Fri, 23 Nov 2018 17:49:30 +0900	[thread overview]
Message-ID: <CAK7LNATiis8ci+bczBsPWHfVSC=pePnpTNddQigJ9uVWOtqDww@mail.gmail.com> (raw)
In-Reply-To: <20181116143127.13875-1-s.hauer@pengutronix.de>

On Fri, Nov 16, 2018 at 11:31 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> The socfpga xload images are limited to 64KiB. This doesn't fit if
> multiple boards are selected. The reason is that we include huge
> C files and arrays in the early init code which get compiled once
> for each board. -ffunction-sections is without effect here since all
> functions have the same name and hence we get the same function
> multiple times in the same section.
>
> To overcome this we surround all function names with a SECT() macro which
> is used to add a board specific prefix to the section names. This way
> -ffunction-sections can now do its work and discard unused functions.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>


I just accidentally stopped by this commit.

It is a good thing that you noticed dead code elimination
(-ffunction-sections -fdata-sections, --gc-sections)
does not work if the same symbol names are used
in the conventional incremental linking
Linux kernel used to use.

As you notice, this is a potential problem
of CONFIG_PBL_MULTI_IMAGES,
and I know the right solution.


Since Linux v4.13 (commit 98ced886dd79a),
Linux kernel build system uses thin archive,
where Kbuild uses $(AR) rcSTP instead of $(LD) -r
to combine built-in objects.

With this, the final link stage does the right thing to do
for --gc-sections.

Besides, thin archive is faster,
and saves disk spaces.

If you sync core Makefiles with Linux,
your problem will be solved.





--
Best Regards
Masahiro Yamada

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2018-11-23  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 14:31 Sascha Hauer
2018-11-19  8:30 ` Steffen Trumtrar
2018-11-23  8:49 ` Masahiro Yamada [this message]
2018-11-26  9:46   ` Sascha Hauer

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='CAK7LNATiis8ci+bczBsPWHfVSC=pePnpTNddQigJ9uVWOtqDww@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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