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	chore(pauth): remove redundant pauth_disable_el3() call	2023-04-28 08:09:14 +01:00
bl2.ld.S	feat(build): check that .text section starts at page boundary	2023-11-06 23:22:25 +03:00
bl2.mk	feat(fvp): capture timestamps in bl stages	2023-09-07 23:38:43 +02:00
bl2_el3.ld.S	feat(build): check that .text section starts at page boundary	2023-11-06 23:22:25 +03:00
bl2_image_load_v2.c	fix(bl2): correct messages with image_id	2022-02-15 18:09:51 +01:00
bl2_main.c	feat(fvp): capture timestamps in bl stages	2023-09-07 23:38:43 +02:00
bl2_private.h	Move BL1 and BL2 private defines to bl_common.h	2019-01-15 13:52:32 +00:00