GPU and CPU compilation possible #117
Open
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
|
Well, alpaka is not compiling with gcc 5.2. It is time for a module system on our drone server. |
|
Alpaka could also be fixed to be compileable with gcc 5.2 |
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.
This PR provides HASEonGPU the ability to compile for CPU and GPU. The GPU back-end is used when CUDA was selected by compile time option, otherwise the CPU back-end is used. It is currently no possible to select the back-end on run-time, because nvcc is not able fully compile the CPU back-end code of alpaka.
This PR needs to be followed by performance checks.