Skip to content
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

Fix Build Warnings for AArch64 #2242

Merged
merged 2 commits into from
Feb 5, 2025

Conversation

Antonios-C
Copy link
Contributor

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]

@CLAassistant
Copy link

CLAassistant commented Jan 22, 2025

CLA assistant check
All committers have signed the CLA.

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 Antonios-C force-pushed the crossCompilerWarnings branch from 50c69d4 to e31460e Compare January 22, 2025 19:51
Copy link
Member

@svenvh svenvh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for going through all of these!

test_conformance/images/clCopyImage/test_loops.cpp Outdated Show resolved Hide resolved
Remove the default case, so it will be possible to catch compiler errors when
the enum is extended.

Signed-off-by: Antonios Christidis <[email protected]>
@Antonios-C
Copy link
Contributor Author

@svenvh What is the process for getting pull requests merged after they have been approved ?

@svenvh
Copy link
Member

svenvh commented Feb 5, 2025

These fixes should be uncontroversial; merging.

@svenvh svenvh merged commit 2031e21 into KhronosGroup:main Feb 5, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants