-
Notifications
You must be signed in to change notification settings - Fork 16
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
Rename GC_ENABLE_GPU to GC_ENABLE_IMEX & clean up properties usage #205
Conversation
Overall LGTM. Do we need GC_ENABLE_GPU in the future, when we introduce non-IMEX GPU features? |
@@ -1,2 +1,2 @@ | |||
if not config.gc_use_gpu: | |||
if not config.gc_use_imex: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This subdirectory was originally designed for general GPU tests. Shall we rename this directory to IMEX? Or maybe we can add a new subdirectory in test/gc/transforms/GPU/IMEX ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, so it should either be less strict and allow some of the tests to run. Another option is to split the tests into different folders. Let's decide once we have them.
@@ -1,2 +1,2 @@ | |||
if not config.gc_use_gpu: | |||
if not config.gc_use_imex: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to above... Do we need to distinguish general GPU tests from IMEX tests?
I don't yet see a need for that unless it steers some runtime dependencies, unavailable on a cpu-only machine. |
This cleans up the gpu passes target and prepares for the default pipeline.