arm-trusted-firmware/bl32/sp_min
Andrey Skvortsov 3d6edc325c feat(build): check that .text section starts at page boundary
Linker may decide to put new unspecified sections before .text
section. That will cause non-working image, because entry point isn't
at __BLXX_START__. Device just not booted with such image.

This happened for example with .note.gnu.build-id section generated
for LTO build in some cases. Now linker will report this situation as
an error.

```
/usr/lib/gcc-cross/aarch64-linux-gnu/13/../../../../aarch64-linux-gnu/bin/ld: .text is not aligned on a page boundary.
collect2: error: ld returned 1 exit status
```

Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
Change-Id: I5ae46ddd1e6e431e1df1715d1d301f6dd7181cc7
2023-11-06 23:22:25 +03:00
..
aarch32 fix(bl32): avoid clearing argument registers in RESET_TO_SP_MIN case 2023-08-04 16:02:59 +02:00
sp_min.ld.S feat(build): check that .text section starts at page boundary 2023-11-06 23:22:25 +03:00
sp_min.mk fix(bl32): always include arm_arch_svc in SP_MIN 2023-08-04 16:02:59 +02:00
sp_min_main.c feat(bl32): print entry point before exiting SP_MIN 2023-08-04 16:02:59 +02:00
sp_min_private.h sp_min: make sp_min_warm_entrypoint public 2019-04-25 13:37:56 +02:00
wa_cve_2017_5715_bpiall.S Rename symbols and files relating to CVE-2017-5715 2018-05-23 12:45:48 +01:00
wa_cve_2017_5715_icache_inv.S Rename symbols and files relating to CVE-2017-5715 2018-05-23 12:45:48 +01:00