Use this larger boundary to ensure that linker lists at least start on the
maximum possible alignment boundary. See also the CONFIG_LINKER_LIST_ALIGN
setting, but that is host-arch-specific, so it seems better to use the
largest value for every host architecture.

Signed-off-by: Simon Glass <s...@chromium.org>
---

 arch/sandbox/cpu/u-boot-spl.lds | 2 +-
 arch/sandbox/cpu/u-boot.lds     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/sandbox/cpu/u-boot-spl.lds b/arch/sandbox/cpu/u-boot-spl.lds
index 6754f4ef6cc..206e265e74b 100644
--- a/arch/sandbox/cpu/u-boot-spl.lds
+++ b/arch/sandbox/cpu/u-boot-spl.lds
@@ -8,7 +8,7 @@
 SECTIONS
 {
 
-       . = ALIGN(4);
+       . = ALIGN(32);
        .u_boot_list : {
                KEEP(*(SORT(.u_boot_list*)));
        }
diff --git a/arch/sandbox/cpu/u-boot.lds b/arch/sandbox/cpu/u-boot.lds
index 6d710618f59..92e834a8d2b 100644
--- a/arch/sandbox/cpu/u-boot.lds
+++ b/arch/sandbox/cpu/u-boot.lds
@@ -8,7 +8,7 @@
 SECTIONS
 {
 
-       . = ALIGN(4);
+       . = ALIGN(32);
        .u_boot_list : {
                KEEP(*(SORT(.u_boot_list*)));
        }
-- 
2.35.1.1021.g381101b075-goog

Reply via email to