celerity-runtime icon indicating copy to clipboard operation
celerity-runtime copied to clipboard

High-level C++ for Accelerator Clusters

Results 26 celerity-runtime issues
Sort by recently updated
recently updated
newest added

Currently, there is no native way to get results out of a Celerity buffer and back into the main thread at the end of a Celerity program. The current workaround...

Side-effects introduced in #68 currently always serialize execution between host tasks affecting the same host object. Since the precise interactions within the host task are entirely user-defined, this can be...

For now this only shows the buffer names plus ids instead of just ids when printing the command graph, but in a future it could also be used for instrumenting...

The idea behind this is to able to simulate a run to analyze behavior and how would celerity scale to larger amounts nodes, without necessarily having those nodes. For this...

I've [parsed](https://gist.github.com/psalz/5f936894a451f25e2b9d1d6f66915307) all clang-tidy diagnostics generated with the following checks enabled: ``` -*, bugprone-*, clang-analyzer-*, clang-diagnostic-*, cppcoreguidelines-*, mpi-*, performance-*, readability-* ``` and those are the results: ``` Found 2137 diagnostics...

Work in progress open for discussion. I currently vendored the args library directly into the benchmarks folder, which is probably not what we want. I do however expect these benchmarks...

[#107](https://github.com/celerity/celerity-runtime/pull/107) has frontend benchmarks that do not instantiate the entire runtime. Low hanging fruit: - Currently, 13% of the time is spent in iostreams for creating the CDAG debug labels....

SYCL 2020 introduces a new canonical namespace `::sycl`. While the old `::cl::sycl` namespace remains available for backwards compatibility, there is no reason for us to keep using it. The only...