Skip to content

Neoverse code cleanup for building with -DENABLE_WARNINGS=ON.#529

Merged
tpatki merged 1 commit intodevfrom
neoverse_fixes
Apr 4, 2025
Merged

Neoverse code cleanup for building with -DENABLE_WARNINGS=ON.#529
tpatki merged 1 commit intodevfrom
neoverse_fixes

Conversation

@tpatki
Copy link
Copy Markdown
Member

@tpatki tpatki commented Mar 11, 2024

Description

Cleanup for -Werror-unused-parameter , need to figure out how far to propogate the change and check where to test with @amarathe84.

Fixes #526.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature/architecture support (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Build/CI update

How Has This Been Tested?

  • Juno r2
  • neoverse system?

Checklist:

  • I have run ./scripts/check-code-format.sh and confirm my code code follows the style guidelines of variorum
  • I have added comments in my code
  • My changes generate no new warnings (build with -DENABLE_WARNINGS=ON)
  • New and existing unit tests pass with my changes

Thank you for taking the time to contribute to Variorum!

@slabasan slabasan added the status-approved No more revisions are required on this PR and it is ready for merge label Apr 4, 2025
@tpatki tpatki merged commit 7da24d8 into dev Apr 4, 2025
9 checks passed
@tpatki tpatki deleted the neoverse_fixes branch April 4, 2025 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status-approved No more revisions are required on this PR and it is ready for merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Check ARM Neoverse build with -DENABLE_WARNINGS=ON

2 participants