[Fix] DaCe build system should be tied more closely to existing configuration #241
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
romanc
approved these changes
Sep 24, 2025
Collaborator
romanc
left a comment
There was a problem hiding this comment.
Looking forward to building this properly in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
GT4Py as a flag
GT4PY_COMPILE_OPT_LEVELthat directs-Ocompiler flags. We have tied it in to the compilation level for DaCe within their CMake system. But we haven't tied it fully and this PR fixes that.In a subsequent PR we should introduce a NDSL level configuration for optimization that drives both the GT4Py and DaCe sub-configuration.