From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Sun, 10 Jun 2018 21:11:05 +0200 Subject: [U-Boot] [PATCH 04/18] x86: efi: payload: Enforce toolchain to generate 64-bit EFI payload stub codes In-Reply-To: <1528637118-32739-5-git-send-email-bmeng.cn@gmail.com> References: <1528637118-32739-1-git-send-email-bmeng.cn@gmail.com> <1528637118-32739-5-git-send-email-bmeng.cn@gmail.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 10.06.18 15:25, Bin Meng wrote: > Attempting to use a toolchain that is preconfigured to generate code > for the 32-bit architecture (i386), for example, the i386-linux-gcc > toolchain on kernel.org, to compile the 64-bit EFI payload does not > build. This updates the makefile fragments to ensure '-m64' is passed > to toolchain when building the 64-bit EFI payload stub codes. > > Signed-off-by: Bin Meng Is there any sane reason to keep the split between EFI and U-Boot long size alive? The x86_64 U-Boot port is getting along reasonably well from what I can tell and 32bit UEFI implementations on 64-bit hosts are dying out. So can't we just remove all of that cruft altogether instead and just have x86_64 U-Boot with 64bit EFI stub and i386 U-Boot with 32bit EFI stub as only combinations? That would dramatically simplify the code. Alex