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

feat[next][dace]: make canonical representation of field domain optional #1476

Merged
merged 3 commits into from
Feb 29, 2024

Conversation

edopao
Copy link
Contributor

@edopao edopao commented Feb 28, 2024

Baseline implementation of DaCe backend was reordering the dimensions in field domain based on alphabetical order. This is the canonical representation of field domain, and provides the advantage of not requiring regenerating the SDFG for different memory layouts of field arguments. Besides, the code for accessing a field is simple, because all field domains are assumed to follow the same layout.

However, the canonical representation poses an obstacle to the realization of module-level SDFGs, because it requires an additional conversion step of all array arguments before calling the SDFG. Therefore, we make the canonical representation optional. Note that this change should not have any performance impact, because the real memory layout of field arrays is not modified.

@edopao edopao marked this pull request as ready for review February 29, 2024 07:06
@edopao edopao merged commit ae9c203 into GridTools:main Feb 29, 2024
31 checks passed
@edopao edopao deleted the dace-no_sort_field_dims branch February 29, 2024 07:42
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.

2 participants