You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Figure out how to achieve ZigLLVMTargetMachineEmitToFile via passing an LLVM bitcode file (.bc) to the Clang command line. This may require getting patches landed upstream.
challenge: enabling tsan
challenge: enabling sancov
challenge: setting the options of ZigLLVMCoverageOptions, in particular with the desired pass orderings
challenge: enabling IR verification
how to do equivalent of ZigLLVMSetOptBisectLimit with clang CLI
This issue mainly concerns transitioning from calling into LLVM as a library into calling into Clang as a standalone executable. For the purposes of this issue it doesn't matter whether Clang is exposed via a sub-command of the zig binary (zig clang), or whether clang is found at runtime. The point is that object files are produced by creating bitcode files and then invoking clang as a separate process to compile those bitcode files into object files.
Issue close criteria:
src/zig_llvm.cpp,src/zig_llvm.h, andsrc/codegen/llvm/bindings.zigPrerequisite of:
Depends on:
ZigLLVMTargetMachineEmitToFilevia passing an LLVM bitcode file (.bc) to the Clang command line. This may require getting patches landed upstream.ZigLLVMSetOptBisectLimitwith clang CLIThis issue mainly concerns transitioning from calling into LLVM as a library into calling into Clang as a standalone executable. For the purposes of this issue it doesn't matter whether Clang is exposed via a sub-command of the zig binary (
zig clang), or whetherclangis found at runtime. The point is that object files are produced by creating bitcode files and then invoking clang as a separate process to compile those bitcode files into object files.