Hi Heitaum, Thanks for reporting this.

Hi Heitbaum, could you tell me which toolchain you're using to build TF-A? The latest Arm GNU AArch64 toolchain is 11.3.Rel1, which packages binutils-2.38 and therefore compiles successfully, so I'm currently unable to reproduce this error.

Hey Chris, I may have raised the bug wrong we are tracking internally as its binutils-2.39, sorry!

@joannafarley-arm

Adding that the linking warns about both rwx-sections and execstack for bl2 too.
So both are needed or the linking needs to be fixed.
I think the no-warn flags are only available to newer tools, so defaulting to them will probably break things.

I can confirm this occurs with binutils 2.39. We (coreboot) are trying to update binutils from our toolchain and we are about to adjust our build system. --no-warn-rwx-segment fixes the issue. https://review.coreboot.org/c/coreboot/+/66920

Would be great if this could be fixed in your repository, since most likely many people will get this error sooner or later.

What's the status of this? Currently trying to build TF-A against the bookworm toolchain, and there the warning is even fatal. For now I'm working around it with this patch:

diff --git a/Makefile b/Makefile
index c4350dc16..07b4d5ccb 100644
--- a/Makefile
+++ b/Makefile
@@ -427,6 +427,7 @@ else ifneq ($(findstring gcc,$(notdir $(LD))),)
 # Pass ld options with Wl or Xlinker switches
 TF_LDFLAGS		+=	-Wl,--fatal-warnings -O1
 TF_LDFLAGS		+=	-Wl,--gc-sections
+TF_LDFLAGS		+=	-Wl,--no-warn-rwx-segment
 ifeq ($(ENABLE_LTO),1)
 	ifeq (${ARCH},aarch64)
 		TF_LDFLAGS	+=	-flto -fuse-linker-plugin
@@ -444,6 +445,7 @@ TF_LDFLAGS		+=	$(subst --,-Xlinker --,$(TF_LDFLAGS_$(ARCH)))
 else
 TF_LDFLAGS		+=	--fatal-warnings -O1
 TF_LDFLAGS		+=	--gc-sections
+TF_LDFLAGS		+=	--no-warn-rwx-segment
 # ld.lld doesn't recognize the errata flags,
 # therefore don't add those in that case
 ifeq ($(findstring ld.lld,$(notdir $(LD))),)

But before proposing this for upstream, I'd like to know if the issue can't be solved by actually not marking the executable section(s) writable.

Hi Jan, sorry for the delay. This is currently in progress under the mixed-rwx topic: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18661/5

Thanks, good to know. So, 2.9 will likely carry a fix? Is there a better patch I can use already (the one referenced does not directly appear to solve the issue)?

The patch stack is still a work in progress so BL1 is the only fixed image so far, but BL2 and BL31 need the same treatment. Your best bet until I get around to applying these fixes to the remaining images is the current workaround (TF_LDFLAGS="--no-warn-rwx-segment").

Please see https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/19401 which should fix this for all targets.

In T996#12020, @bith3ad wrote:

Please see https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/19401 which should fix this for all targets.

I can confirm that the fix is included in 2.9-rc0

Building with binutils-2.40 and gcc-13.1.0

This might be related to https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18661/5 mapquest driving directions

Thank you for sharing useful information about ELF Linker Immaculate grid

This might be related to https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18661/5 tiny fishing

This link is useful.

Thanks to reading this article, I have gained new knowledge, thank you very much moto x3m bike race game

Review the compilation flags being used, and among us online ensure they do not enable any unusual or unsafe permissions.

nice job guys
آهنگ

In your case, the warning is related to a LOAD segment having RWX (Read, Write, Execute) permissions, and it's being treated as an error due to the subway surfers online use of --fatal-warnings during the build. To address this issue, you can use the --no-warn-rwx-segment option to disable the warning about the RWX permissions. This option is mentioned in the commit you provided.

In case if you are still facing that issue do hire angularjs developers like me.

We used ChatGPT in developing brain game like Contexto and Numberle, Flagle. It can be really powerful and useful tool.

During the detailing process, professionals may identify potential issues or areas that require maintenance or repair. They can provide you with valuable insights and recommendations, helping you address any concerns before they car body detailing near me escalate into more significant problems. This proactive approach can save you from costly repairs down the line.

Thanks, good to know. موزیک