summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Hochstein <tom.hochstein@nxp.com>2022-07-25 15:29:07 -0500
committergithub-actions[bot] <github-actions[bot]@users.noreply.github.com>2022-07-25 20:46:47 +0000
commitd630b57f798f04feebed5d939cec256fbea2f6e5 (patch)
tree05ed36a4d1947c1ca0e60159a4fd2d77f41f1193
parent2e785f257ad98581b684f0e32f6d4bb96faefb10 (diff)
downloadmeta-freescale-backport-1142-to-kirkstone.tar.gz
imx-atf: Refine array-bounds patch commit messagebackport-1142-to-kirkstone
Refine the commit message for the patch 0001-Makefile-Suppress-array-bounds-error.patch, making it clear that the patch is a workaround for an issue in GCC 12, and that the issue is fixed in GCC 13. Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> (cherry picked from commit 20586ab8aeb5ac9f71ab05b449fa25b406c5a2b7)
-rw-r--r--recipes-bsp/imx-atf/imx-atf/0001-Makefile-Suppress-array-bounds-error.patch15
1 files changed, 10 insertions, 5 deletions
diff --git a/recipes-bsp/imx-atf/imx-atf/0001-Makefile-Suppress-array-bounds-error.patch b/recipes-bsp/imx-atf/imx-atf/0001-Makefile-Suppress-array-bounds-error.patch
index 37b5ce6f..c7ace225 100644
--- a/recipes-bsp/imx-atf/imx-atf/0001-Makefile-Suppress-array-bounds-error.patch
+++ b/recipes-bsp/imx-atf/imx-atf/0001-Makefile-Suppress-array-bounds-error.patch
@@ -3,8 +3,8 @@ From: Tom Hochstein <tom.hochstein@nxp.com>
3Date: Mon, 16 May 2022 13:45:16 -0500 3Date: Mon, 16 May 2022 13:45:16 -0500
4Subject: [PATCH] Makefile: Suppress array-bounds error 4Subject: [PATCH] Makefile: Suppress array-bounds error
5 5
6The array-bounds error is triggered now in cases where it was silent before, 6The array-bounds error is triggered now in cases where it was silent
7causing errors like: 7before, causing errors like:
8 8
9``` 9```
10plat/imx/imx8m/hab.c: In function 'imx_hab_handler': 10plat/imx/imx8m/hab.c: In function 'imx_hab_handler':
@@ -13,10 +13,15 @@ plat/imx/imx8m/hab.c:64:57: error: array subscript 0 is outside array bounds of
13 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 13 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
14``` 14```
15 15
16It appears that these new cases will be silenced soon in gcc [1], so for 16The error is a false-positive and is entered as a bug [1]. The problem
17now just silence the warning locally as a workaround. 17is fixed partially in GCC 12 and fully in GCC 13 [2].
18 18
19[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578#c39 19The partial fix does not work here because the constant addresses used
20are less than the 4kB boundary chosen for the partial fix, so suppress
21the error until GCC is upgraded to 13.
22
23[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578
24[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578#c39
20 25
21Upstream-Status: Inappropriate [other] 26Upstream-Status: Inappropriate [other]
22Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> 27Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>