bazel-contrib / bazel-contrib/rules_cuda
Unexpected `INFO: From ...`
- Dominant language
- Starlark
- Stars
- 122
- Forks
- 73
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 7
Description
On Windows:
```
INFO: From Compiling examples/rdc/b.cu:
b.cu
INFO: From Compiling examples/rdc/b.cu:
b.cu
INFO: From Compiling examples/rdc/a.cu:
a.cu
INFO: From Compiling examples/rdc/a.cu:
a.cu
INFO: From Compiling examples/basic/kernel.cu:
kernel.cu
INFO: From Compiling examples/basic/kernel.cu:
kernel.cu
INFO: From Device linking bazel-out/x64_windows-fastbuild/bin/examples/rdc/librdc_dlink.rdc.obj:
a.rdc.obj
b.rdc.obj
INFO: From Device linking bazel-out/x64_windows-fastbuild/bin/examples/rdc/librdc_dlink.rdc.pic.obj:
a.rdc.pic.obj
b.rdc.pic.obj
...
```
It comes from `cl.exe` blindly output input file name to stdout
Unless https://togithub.com/bazelbuild/bazel/issues/5511 or https://developercommunity.visualstudio.com/t/allow-having-clexe-not-print-the-compiled-source-f/717761 is addressed.
Contributor guide
Research direction
Reproduce the Windows build output using the examples/rdc and examples/basic targets, then inspect how cl.exe is invoked by the CUDA rules. Compare the emitted filenames with the linked Bazel and Visual Studio issues; done would require a confirmed in-repository way to prevent the unwanted output or evidence that an upstream fix resolves it.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100