It is obviously correct but cannot such change have some stable API impact?
llvm/include/llvm/IR/DebugInfoFlags.def
Used a simple shell script to sync it.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
| Time | Test | |
|---|---|---|
| 37,140 ms | x64 debian > libFuzzer.libFuzzer::fork.test |
Event Timeline
@jberdine I had to update the OCaml bindings as otherwise a buildbot failed.
/b/1/openmp-clang-x86_64-linux-debian/llvm.build/bindings/ocaml/debuginfo/debuginfo_ocaml.c: In function ‘map_DIFlag’:
/b/1/openmp-clang-x86_64-linux-debian/llvm.build/bindings/ocaml/debuginfo/debuginfo_ocaml.c:104:12: error: ‘LLVMDIFlagReserved’ undeclared (first use in this function); did you mean
‘i_DIFlagReserved’?
return LLVMDIFlagReserved;
^~~~~~~~~~~~~~~~~~
i_DIFlagReservedI have fixed it based on a local build with OCaml (Fedora 34 x86_64). This is not a full OCaml sync with llvm/include/llvm/IR/DebugInfoFlags.def, just the part required to sync llvm/include/llvm-c/DebugInfo.h.
@jberdine Are you fine with this change?
LGTM. No-one should be using enum tags named "Reserved" so I'm not worried about compatibility.
Is there a comment or something that would have pointed you to the debuginfo_ocaml.c change before the buildbots complained?
CC @vaivaswatha for info.
| llvm/include/llvm/IR/DebugInfoFlags.def | ||
|---|---|---|
| 30 | Do you mean something like this? | |
| llvm/include/llvm/IR/DebugInfoFlags.def | ||
|---|---|---|
| 30 | Yes, that seems good. I don't know if others want the core sources "polluted" :-) by references to other language bindings though. | |
clang-tidy: error: 'caml/memory.h' file not found [clang-diagnostic-error]
not useful