Much like other LLVM binary utilities, llvm-cov has a symlink compatibility feature where it runs in gcov compatibility mode if the binary name ends in gcov. This is identical to invoking llvm-cov gcov ....
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Is it strictly ends with, or do things like file extensions, version numbers etc have an impact? See the additional test cases in https://github.com/llvm/llvm-project/blob/main/llvm/test/tools/llvm-objcopy/tool-name.test.
Comment Actions
Strictly ends with. See https://github.com/llvm/llvm-project/blob/98575708da9544ccab8939fece9c3d638a32f09f/llvm/tools/llvm-cov/llvm-cov.cpp#L63.
I could land this as-is and copy that from llvm-objcopy so "llvm-gcov-10" would be recognized. Although I don't know how many people are relying on this -- the existence of this doesn't even seem to be in cmake configs (i.e. we don't produce *gcov symlinks like we do for llvm-strip).