No description
Find a file
Andrey Skvortsov 31f80efeef fix(build): enforce single partition for LTO build
For example, build for PLAT=fvp SPD=spmd fails with a following error
when LTO is enabled using GCC 13.2.1:

  aarch64-none-elf/bin/ld: /tmp/ccrG0Z8D.ltrans0.ltrans.o: in function `spmd_smc_forward':
  arm-trusted-firmware/services/std_svc/spmd/spmd_main.c:749:(.text+0xbe50): undefined reference to `rdist_ctx'
  aarch64-none-elf/bin/ld: arm-trusted-firmware/services/std_svc/spmd/spmd_main.c:749:(.text+0xbe58): undefined reference to `dist_ctx'
  collect2: error: ld returned 1 exit status

Access to rdist_ctx and dist_ctx is defined using inline assembler
like
 __asm__ volatile ("ldr %0, =rdist_ctx" : "=r" (v) : "X" (rdist_ctx));

Access assembler function definitions moved to a different ltrans then
actual variables. Partitioner doesn't take into account defined and
used symbols in inline assembler. Depending on compiler partitioner
decision the same code builds for some platforms successfully.

This is a known gcc problem
1. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57703
2. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46820

TF-A source code isn't that big and enforcing single partitioning will
not affect build performance, but will fix problems with 'undefined
references' related to inline assembler.

Change-Id: I72955ab0318f72b588d3a246824f99a48a92d8ef
Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
2024-02-24 00:42:50 +03:00
.husky style(hooks): copyright year check as per author email 2024-01-19 14:29:29 +01:00
bl1 build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl2 build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl2u build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl31 build: use toolchain identifiers in conditions 2024-02-06 11:14:52 +00:00
bl32 Merge "build: use toolchain identifiers in conditions" into integration 2024-02-20 16:06:52 +01:00
common feat(mte): add mte2 feat 2024-02-12 08:20:01 -06:00
docs Merge "docs(threat_model): mark power analysis threats out-of-scope" into integration 2024-02-20 17:04:03 +01:00
drivers chore(ufs): refactor ufs_get_device_info 2024-02-20 02:19:19 -08:00
fdts refactor(tc): remap console logs 2024-02-13 14:57:15 +00:00
include refactor(context-mgmt): move EL1 save/restore routines into C 2024-02-22 10:34:40 +00:00
lib Merge "fix(cm): update gic el2 sysregs save/restore mechanism" into integration 2024-02-22 11:58:43 +01:00
licenses docs(license): rectify arm-gic.h license 2021-04-26 12:36:00 +01:00
make_helpers build: correct minor toolchain documentation error 2024-02-21 14:06:03 +00:00
plat fix(rockchip): add support for building with LTO enabled 2024-02-24 00:42:50 +03:00
services refactor(context-mgmt): remove el1_context routines from RMM 2024-02-22 10:34:52 +00:00
tools build: use new toolchain variables for tools 2024-02-06 11:14:52 +00:00
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch 2019-07-12 11:06:24 +01:00
.commitlintrc.js build(commitlint): make the scope optional 2022-05-03 11:06:50 +02:00
.cz.json refactor(hooks): replace cz-conventional-changelog with cz-commitlint 2022-01-24 12:55:00 +00:00
.editorconfig .editorconfig: set max line length to 100 2020-12-03 15:39:23 +00:00
.gitignore fix: .gitignore to include memory tools 2023-08-11 11:49:53 +01:00
.gitreview Specify integration as the default branch for git-review 2020-04-02 07:57:17 +00:00
.nvmrc build(npm): add NVM version file 2022-10-10 13:24:22 +01:00
.readthedocs.yaml fix: use rsvg-convert as the conversion backend 2023-07-28 12:37:49 +01:00
.versionrc.js fix(build): properly manage versions in .versionrc.js 2024-02-08 19:24:33 +01:00
changelog.yaml Merge changes from topics "rcar-tools-fix", "toolchain-cleanup" into integration 2024-01-24 16:11:22 +01:00
dco.txt Drop requirement for CLA in contribution.md 2016-09-27 21:52:03 +01:00
license.rst doc: De-duplicate readme and license files 2019-10-08 16:36:15 +00:00
Makefile fix(build): enforce single partition for LTO build 2024-02-24 00:42:50 +03:00
package-lock.json docs(changelog): changelog for v2.10 release 2023-11-22 11:52:02 +00:00
package.json docs(changelog): changelog for v2.10 release 2023-11-22 11:52:02 +00:00
poetry.lock build(poetry): bump requests from 2.30.0 to 2.31.0 2023-09-06 14:51:49 +00:00
pyproject.toml docs(changelog): changelog for v2.10 release 2023-11-22 11:52:02 +00:00
readme.rst docs: fix link to TBBR specification 2024-02-02 15:31:12 +01:00

Trusted Firmware-A
==================

Trusted Firmware-A (TF-A) is a reference implementation of secure world software
for `Arm A-Profile architectures`_ (Armv8-A and Armv7-A), including an Exception
Level 3 (EL3) `Secure Monitor`_. It provides a suitable starting point for
productization of secure world boot and runtime firmware, in either the AArch32
or AArch64 execution states.

TF-A implements Arm interface standards, including:

-  `Power State Coordination Interface (PSCI)`_
-  `Trusted Board Boot Requirements CLIENT (TBBR-CLIENT)`_
-  `SMC Calling Convention`_
-  `System Control and Management Interface (SCMI)`_
-  `Software Delegated Exception Interface (SDEI)`_

The code is designed to be portable and reusable across hardware platforms and
software models that are based on the Armv8-A and Armv7-A architectures.

In collaboration with interested parties, we will continue to enhance TF-A
with reference implementations of Arm standards to benefit developers working
with Armv7-A and Armv8-A TrustZone technology.

Users are encouraged to do their own security validation, including penetration
testing, on any secure world code derived from TF-A.

More Info and Documentation
---------------------------

To find out more about Trusted Firmware-A, please `view the full documentation`_
that is available through `trustedfirmware.org`_.

--------------

*Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.*

.. _Armv7-A and Armv8-A: https://developer.arm.com/products/architecture/a-profile
.. _Secure Monitor: http://www.arm.com/products/processors/technologies/trustzone/tee-smc.php
.. _Power State Coordination Interface (PSCI): PSCI_
.. _PSCI: http://infocenter.arm.com/help/topic/com.arm.doc.den0022d/Power_State_Coordination_Interface_PDD_v1_1_DEN0022D.pdf
.. _Trusted Board Boot Requirements CLIENT (TBBR-CLIENT): https://developer.arm.com/docs/den0006/latest
.. _SMC Calling Convention: http://infocenter.arm.com/help/topic/com.arm.doc.den0028b/ARM_DEN0028B_SMC_Calling_Convention.pdf
.. _System Control and Management Interface (SCMI): SCMI_
.. _SCMI: http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/DEN0056A_System_Control_and_Management_Interface.pdf
.. _Software Delegated Exception Interface (SDEI): SDEI_
.. _SDEI: http://infocenter.arm.com/help/topic/com.arm.doc.den0054a/ARM_DEN0054A_Software_Delegated_Exception_Interface.pdf
.. _Arm A-Profile architectures: https://developer.arm.com/architectures/cpu-architecture/a-profile
.. _view the full documentation: https://www.trustedfirmware.org/docs/tf-a
.. _trustedfirmware.org: http://www.trustedfirmware.org