Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
Thanks for looking at it.
I'm using llvm libraries in a sample application and on some occasions would like to print debug output from more than one module, like this:
setCurrentDebugTypes({"dyld", "regalloc"});
Currently I can't do this because setCurrentDebugType() allows debugging only one module
Unfortunately I don't have a clue how to write unit test for this, but I think the change is straightforward.
Maybe you can try writing a unit test, no?
Do you have an idea how to do this? This is C++ library function not invoked anywhere inside llvm. I tried to find any test for *setCurrentDebugType(const char *)* (existing one), but looks like there is none either.
You can probably model it after any other unit test for the code living in Support/. If the original function is not tested, it's probably worth a test for that as well, if you don't mind/have bandwidth for. If you still can't find it, I'll provide a pointer.
Sorry for being a little pedantic here, but it's not uncommon for me to go around and remove code considered "dead" in the tree (because unused/untested) and 6 months later receive a mail from somebody with an out-of-tree backend/code complaining I broke their product. So, keeping in-tree tests is at least a way to differentiate between code that's obviously dead and code that's used by somewhere but doesn't live in-tree.