arm-trusted-firmware/bl1
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 feat(debug): add helpers for aborts on AARCH32 2022-10-03 14:42:40 +02:00
aarch64 Merge changes from topic "bk/clearups" into integration 2023-06-07 10:13:17 +02:00
tbbr Coverity: remove unnecessary header file includes 2020-02-04 10:23:51 -06:00
bl1.ld.S feat(build): check that .text section starts at page boundary 2023-11-06 23:22:25 +03:00
bl1.mk feat(fvp): capture timestamps in bl stages 2023-09-07 23:38:43 +02:00
bl1_fwu.c style: remove useless trailing semicolon and line continuations 2023-03-09 14:59:08 +01:00
bl1_main.c feat(fvp): capture timestamps in bl stages 2023-09-07 23:38:43 +02:00
bl1_private.h chore(bl1): remove redundant bl1_arch_next_el_setup 2023-04-28 08:09:14 +01:00