forked from mpaland/printf
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Support CUDA host-side execution #12
Labels
enhancement
New feature or request
Comments
eyalroz
pushed a commit
that referenced
this issue
Jul 6, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc.
eyalroz
pushed a commit
that referenced
this issue
Jul 10, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Jul 11, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Jul 12, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Oct 20, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Oct 20, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Oct 25, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Oct 25, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Oct 27, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Oct 27, 2021
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Feb 1, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Feb 24, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Feb 28, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Feb 28, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Feb 28, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Feb 28, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Mar 1, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Apr 20, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Apr 23, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Apr 23, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
eyalroz
pushed a commit
that referenced
this issue
Apr 23, 2022
* Updated the compiler directives for suppressing relevant warnings to also properly work with NVCC. * Test suite "replicated" for CUDA host-side compilation (by including the `.cpp` file from the `.cu` file) * Test suite adapted for CUDA device-side testing - using some invocation wrappering machinery. It's a bit crude but it does the job. * `CMakeLists.txt` for the tests reworked to support CUDA targets, architecture auto-detection, etc. Caveat: At the moment, CUDA testing is only performed using single-block, single-thread grids.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow the printf library to be used in host-side CUDA code (built with nvcc).
This probably doesn't need much real work, but - some warning-avoidance may be necessary, plus a test suite (maybe just replicate the existing one for starters?)
The text was updated successfully, but these errors were encountered: