arm-trusted-firmware/bl31
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
..
aarch64 fix(el3-runtime): restrict lower el EA handlers in FFH mode 2023-11-01 17:46:46 +00:00
bl31.ld.S feat(build): check that .text section starts at page boundary 2023-11-06 23:22:25 +03:00
bl31.mk fix(el3-runtime): restrict lower el EA handlers in FFH mode 2023-11-01 17:46:46 +00:00
bl31_context_mgmt.c feat(rme): add context management changes for FEAT_RME 2021-10-05 18:41:35 +02:00
bl31_main.c refactor(cm): move EL3 registers to global context 2023-10-31 11:18:42 +00:00
bl31_traps.c feat(el3-runtime): handle traps for IMPDEF registers accesses 2023-04-30 11:04:59 +01:00
ehf.c refactor(el3-runtime): plat_ic_has_interrupt_type returns bool 2023-09-25 17:09:15 -05:00
interrupt_mgmt.c refactor(el3-runtime): plat_ic_has_interrupt_type returns bool 2023-09-25 17:09:15 -05:00