From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Glass <sjg@chromium.org>
Date: Sat, 29 Aug 2020 11:19:09 -0600
Subject: Sections .dynamic and .dynsym in UEFI binaries
In-Reply-To: <56072abc-6add-c343-9472-e505ecd1a4b7@gmx.de>
References: <56072abc-6add-c343-9472-e505ecd1a4b7@gmx.de>
Message-ID: <CAPnjgZ1RNurbTLd_k13cqJ5jCEWpsVoxQRqXn=E_L2OHH+vd_Q@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Heinrich,

On Sat, 29 Aug 2020 at 02:31, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>
> Hello Simon,
>
> with commit c7ae3dfdccc1 ("efi: Add support for a hello world test
> program") you added section .dynamic and .dynsym to generated UEFI binaries.
>
> It is unclear to me why those sections should be needed. According to
> https://docs.oracle.com/cd/E23824_01/html/819-0690/chapter6-42444.html
> section .dynamic is only used for dynamic linking.
>
> On RISC-V inclusion of .dynsym leeds to a file that is longer then the
> value of SizeOfImage in the optional header.
>
> On x86 and x86_64 we have a general problem that SizeOfImage does not
> match the actual file size.

I think this was brought over from arch/x86/config.mk

If it still works without it then it is OK to drop those two sections.

Regards,
Simon