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
..
optee	Remove references to old project name from common files	2019-07-10 11:13:00 +01:00
sp_min	feat(build): check that .text section starts at page boundary	2023-11-06 23:22:25 +03:00
tsp	feat(build): check that .text section starts at page boundary	2023-11-06 23:22:25 +03:00