Shorten the build directory -B C:/build can help, but not enough. The same error still occurs.

This issue was spotted by windows users, and here are some workarounds:

Hi Peter,
So far this has been a deliberate design choice to avoid saving/restoring SVE state from EL3 mainly for BL31 footprint reasons (and performance if unconditionally done on each and every world switch). The vector register file ranges from 2KB to 8KB with 8 cores, and linearly scales to as many cores in the system (which can be hundreds in a server chipset). Apart from specific cases under discussion (SPM-MM or EL3 FF-A SPM), it is preferable to do this at lower EL e.g. a TOS at SEL1 (or Hafnium at SEL2). Do you have specific reasons why it cannot be done at lower EL?
You may also want to take a look at those options: ENABLE_SVE_FOR_NS and ENABLE_SVE_FOR_SWD
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/docs/getting_started/build-options.rst#n409
Regards,
Olivier.

I think My custom 1046 doen't support Secure boot.
Doesn't OPTEE work normally only if the Secure boot is supported?

saves ~2KB of code size and can be disabled at build time.

RFC7539 tests for verification as part of the TF-M regression test suite: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/14551

Poly1305 multipart support in the low level driver: https://review.trustedfirmware.org/q/topic:%22poly1305_multipart%22+(status:open%20OR%20status:merged)

Hi Yuezhiran,
We are following this up internally. Could you please let us know what revision of Helios you have and whether you run linux? (Linux doesn't work around any Helios errata currently)

As I understand it from the white paper (v1.6) from developer.arm.com there is research ongoing for the mitigation sequence for the Cortex- A65. Once known I believe TF-A reference mitigation patches will be developed.

I notice that relevant patches have been merged into the mainline branch except A65. will it be uploaded recently ?

Reference implementations of mitigations in TF-A for vulnerabilities in various CPU's were initially made available for public review in Gerrit. These have now after the opportunity for feedback been merged into the mainline branch.

I disabled user ericjonz and deleted his malicious comment. Thanks for bringing to our attention David
don

DO NOT click the link posted by ericjonze.
It is a malicious link.

Working in progress on this. Current low level APIs are not very well versed to be adapted efficiently for multipart cases. I am studying the algorithms first before defining a strategy to implement the multipart APIs and eventually (maybe) rework the low level driver API as well