EnzymeAD / EnzymeAD/Enzyme-JAX
How to handle -Werror errors?
- Dominant language
- MLIR
- Stars
- 131
- Forks
- 53
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 193
Description
I typically find that building against Enzyme-JAX raises Werror errors in code that I have no control over, such as Enzyme-JAX itself (generated code I believe), or stablehlo. Do you have a recommended way of handling this? I've tried
```sh
bazel build \
--copt="-Wno-error=missing-braces" \
--copt="-Wno-error=unused-variable" \
--copt="-Wno-error=unused-result" \
--copt="-Wno-error=missing-braces" \
--copt="-Wno-error=unused-but-set-variable" \
--copt="-Wno-error=return-type" \
--copt="-Wno-error=unused-result" \
//:mylib
```
but that didn't work. The only success I had is to delete
```
copts = [
"-Werror=unused-variable",
"-Werror=unused-result",
"-Werror=missing-braces",
"-Werror=unused-but-set-variable",
"-Werror=return-type",
"-Werror=unused-result",
],
```
from the build config
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the build configuration and its copts list, then reproduce the failure with the shown Bazel command against //:mylib. Compare the warning behavior for Enzyme-JAX and stablehlo generated code; done means an agreed, documented way to handle these -Werror failures without deleting the configured copts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100