From: <rs@ti.com>
To: <raj.khem@gmail.com>
Cc: <Openembedded-devel@lists.openembedded.org>, <afd@ti.com>,
<denis@denix.org>, <reatmon@ti.com>, <detheridge@ti.com>
Subject: [meta-oe][master][PATCH] vulkan-cts: add workaround for createMeshShaderMiscTestsEXT
Date: Mon, 17 Jun 2024 19:52:03 -0500 [thread overview]
Message-ID: <20240618005203.2022725-1-rs@ti.com> (raw)
From: Randolph Sapp <rs@ti.com>
Remove the CXX flag "-O2" for GCC 13 and 14. There's a bug with ARM GCC
that breaks the iteration of "types" in the createMeshShaderMiscTestsEXT
function. This issue is not present for clang or x86_64 GCC 14.
It seems that the array is not initialized before the first iteration.
In testing this can result in a random value being used. This can
manifest in LINES type being processed twice, resulting in the following
error:
FATAL ERROR: Failed to initialize dEQP: Test case with non-unique name
'no_lines' added to group 'misc'.
Signed-off-by: Randolph Sapp <rs@ti.com>
---
meta-oe/recipes-graphics/vk-gl-cts/vulkan-cts_1.3.7.3.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta-oe/recipes-graphics/vk-gl-cts/vulkan-cts_1.3.7.3.bb b/meta-oe/recipes-graphics/vk-gl-cts/vulkan-cts_1.3.7.3.bb
index 1008a5fd4..7492fe9aa 100644
--- a/meta-oe/recipes-graphics/vk-gl-cts/vulkan-cts_1.3.7.3.bb
+++ b/meta-oe/recipes-graphics/vk-gl-cts/vulkan-cts_1.3.7.3.bb
@@ -23,6 +23,9 @@ SRC_URI += "file://0001-cmake-Define-WAYLAND_SCANNER-and-WAYLAND_PROTOCOLS_D.pat
TOOLCHAIN = "gcc"
+# Workaround an optimization bug that breaks createMeshShaderMiscTestsEXT
+OECMAKE_CXX_FLAGS:remove:toolchain-gcc = "-O2"
+
S = "${WORKDIR}/git"
REQUIRED_DISTRO_FEATURES = "vulkan"
--
2.45.1
next reply other threads:[~2024-06-18 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 0:52 rs [this message]
2024-06-18 1:41 ` [meta-oe][master][PATCH] vulkan-cts: add workaround for createMeshShaderMiscTestsEXT Khem Raj
2024-06-18 18:28 ` Denys Dmytriyenko
2024-06-18 18:48 ` Randolph Sapp
2024-06-19 23:32 ` Randolph Sapp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240618005203.2022725-1-rs@ti.com \
--to=rs@ti.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=afd@ti.com \
--cc=denis@denix.org \
--cc=detheridge@ti.com \
--cc=raj.khem@gmail.com \
--cc=reatmon@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.