Outside of compiler-rt (where it's arguably an anti-pattern too),
LLVM tries to keep its build files as simple as possible. See e.g.
llvm/docs/SupportLibrary.rst, "Code Organization".
Details
Details
Diff Detail
Diff Detail
Event Timeline
llvm/include/llvm/Config/config.h.cmake | ||
---|---|---|
350 | There's already a LLVM_HAVE_TF_API in llvm-config.h.cmake. Should LLVM_HAVE_TF_AOT move there, too? (or vice-versa - it wasn't too clear to me which file is for what) | |
llvm/lib/Analysis/CMakeLists.txt | ||
80 | nit: why did LoopUnrollAnalyzer move? if it's a drive-by change (to keep sorting), should LoopNestAnalysis.cpp also move? |
There's already a LLVM_HAVE_TF_API in llvm-config.h.cmake. Should LLVM_HAVE_TF_AOT move there, too?
(or vice-versa - it wasn't too clear to me which file is for what)