================
@@ -99,6 +100,16 @@ URL of repository that hosts code.
Used for links to definition locations.)"),
llvm::cl::cat(ClangDocCategory));
+static llvm::cl::opt<bool> FTimeTrace("ftime-trace", llvm::cl::desc(R"(
+Turn on time profiler. Generates clang-doc-tracing.json)"),
+ llvm::cl::init(false),
+ llvm::cl::cat(ClangDocCategory));
+
+static llvm::cl::opt<int> FTimeGranularity("ftime-gran", llvm::cl::desc(R"(
----------------
ilovepi wrote:
```suggestion
static llvm::cl::opt<int> FTimeGranularity("ftime-granularity",
llvm::cl::desc(R"(
```
I haven't seen this used elsewhere, is it common in other components? I think
its more typical to pick/set the granularity for a tool as a constant. Even if
we keep it, it should be a hidden option.
https://github.com/llvm/llvm-project/pull/97644
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
