-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building for AArch64 fails due to "strict-aliasing" , "maybe-uninitialized" & "stringop-truncation" errors #2234
Comments
Thanks for the report! Do you have more details on the compiler version you're using? |
Hi there ! The compiler version is 13.3. Currently working on fixing the warnings, will make a pull request this week. |
Antonios-C
added a commit
to Antonios-C/OpenCL-CTS
that referenced
this issue
Jan 22, 2025
This commit links to issue (KhronosGroup#2234). When cross-compiling for AArch64, using gcc 13.3, you encounter three warnings types that turn into errors: - maybe-uninitialized - stringop-truncation - strict-aliasing This commit fixes all the warnings found, in regards to the first two rules. To resolve the warnigns due to strict-aliasing, I am editing the CMake build system. Signed-off-by: Antonios Christidis <[email protected]>
Antonios-C
added a commit
to Antonios-C/OpenCL-CTS
that referenced
this issue
Jan 22, 2025
This commit links to issue (KhronosGroup#2234). When cross-compiling for AArch64, using gcc 13.3, you encounter three warnings types that turn into errors: - maybe-uninitialized - stringop-truncation - strict-aliasing This commit fixes all the warnings found, in regards to the first two rules. To resolve the warnigns due to strict-aliasing, I am editing the CMake build system. Signed-off-by: Antonios Christidis <[email protected]>
svenvh
pushed a commit
that referenced
this issue
Feb 5, 2025
This commit links to issue (#2234). When cross-compiling for AArch64, using gcc 13.3, you encounter three warnings types that turn into errors: - maybe-uninitialized - stringop-truncation - strict-aliasing This commit fixes all the warnings found, in regards to the first two rules. To resolve the warnigns due to strict-aliasing, I am editing the CMake build system. Signed-off-by: Antonios Christidis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When building the CTS repo for a AArch64 platform, the build failed due to 3 types of warnings, that turned into errors (-Werror enablement in CMakeLists.txt).
Example "strict-aliasing":
Example "stringop-truncation":
Examples "maybe-uninitialized":
../test_common/harness/imageHelpers.cpp:3564:56: error: 'src_lod' may be used uninitialized [-Werror=maybe-uninitialized]
../test_common/harness/imageHelpers.cpp:3610:56: error: 'dst_lod' may be used uninitialized [-Werror=maybe-uninitialized]
../test_conformance/api/test_wg_suggested_local_work_size.cpp:276:12: error: 'err' may be used uninitialized [-Werror=maybe-uninitialized]
The text was updated successfully, but these errors were encountered: