Aaron Siddhartha Mondal
Aaron Siddhartha Mondal
This is already possible, but we should probably document the workflow. I suspect that this is especially relevant for WSL2 users because the WSL CUDA driver tends to differ from...
We need to address these issues before we can release the next version of `rules_ll`: - [x] https://github.com/eomii/rules_ll/issues/85 - [x] https://github.com/eomii/rules_ll/issues/84 - [ ] https://github.com/eomii/rules_ll/issues/47 - [x] https://github.com/eomii/rules_ll/issues/99 - [...
Playing around with clippy in `rules_rust` made me notice how incredibly convenient it would be to have clang-tidy run as a plugin that just prints warnings like a "regular" compiler...
Doesn't work yet. Just for reference.
The only remote execution image currently provided is the default image which we use for the tests and pin in [rbe/default/config/BUILD](https://github.com/eomii/rules_ll/blob/main/rbe/default/config/BUILD). The default image includes openssl because the examples require...
Attempts to run the tests in CI via remote execution currently doesn't work because Bazel doesn't like to run in a nix-built container. `build` and `run` works, but `test` doesn't,...
It can be tricky to write CUDA/HIP code that at least remotely looks like C++. At the moment the examples are littered with `// NOLINT` directives so that clang-tidy doesn't...
It may be desirable for non-`rules_ll` users to get `bzlmod` support for the original Clang/LLVM Bazel overlay. The files whose contents we may be able to upstream are `ll/extensions.bzl`, `MODULE.bzl`...
https://github.com/NixOS/nixpkgs/issues/224646#issuecomment-1498945232 mentioned that the way we currently import CUDA from nix is outdated. We should change imports from the outdated ```nix pkgs.cudaPackages.cudatoolkit ``` to ```nix cudaPackages.{lib,cuda_foo} ``` @JannisFengler @SpamDoodler This...
Surely there is some workaround. - Ignoring `examples/flake.lock` causes direnv/devenv to break - Committing it would break downstream users because the relative reference to rules_ll via `../` is not reproducible...