search

alpaka-group / alpaka

Abstraction Library for Parallel Kernel Acceleration :llama:
https://alpaka.readthedocs.io
Mozilla Public License 2.0
339 stars 69 forks source link

Compiler Explorer #600

Closed ax3l closed 1 year ago

ax3l commented 5 years ago

We should add alpaka/develop to the libs of Matt Godbolt's compiler explorer: https://godbolt.org/

https://github.com/mattgodbolt/compiler-explorer/wiki/Installed-libraries

Relevant files:

Example PRs:

Needs probably simplified headers: see #601

BenjaminW3 commented 5 years ago

Example project using godbolt as playground

bernhardmgruber commented 2 years ago

I am solving this in LLAMA by creating an amalgamated (single header) llama.hpp on each commit to develop and commit that file to an orphaned branch. That is similar to what we do for github pages. See: https://github.com/alpaka-group/llama#single-header

SimeonEhrig commented 2 years ago

@bernhardmgruber Does the llama header also include alpaka? I also plan to create a single header version for vikunja and I need to resolve this dependency.

bernhardmgruber commented 2 years ago

@SimeonEhrig no, because llama does not depend on alpaka. llama also depends on Boost, and I do not include that. But fortunately, you can just have Boost on compiler explorer with a few clicks. Since vikunja depends on alpaka, I think we would really need to add this to Compiler Explorer as suggested.

bernhardmgruber commented 1 year ago

We have a single header of alpaka now that can be used on godbolt: https://github.com/alpaka-group/alpaka#single-header

I don't think we need alpaka on godbolt directly, since this way we can only have released versions of alpaka, which are scarce and often lag behind tremendously in features. I think most users (and also us devs) want to play with the develop branch on godbolt, or even be able to choose a specific commit to use.

j-stephan commented 1 year ago

Closing as completed.