[llvm-dev] Status of debuginfo-tests
Adrian Prantl via llvm-dev
llvm-dev at lists.llvm.org
Thu Sep 7 11:46:17 PDT 2017
> On Sep 7, 2017, at 11:34 AM, Zachary Turner <zturner at google.com> wrote:
> Even if it were under llvm, that doesn't mean it would have to be part of ninja check-all. Currently we have lldb/test and lldb/unittests, what about a third lldb/dbgtests? Then you could run it as ninja check-dbgtest.
They are not LLDB tests. They end-to-end test that the debug info produced by clang works with the *host* debugger, which can be gdb or lldb. They are part of the CFE tests for this reason.
> Although now that I think about it, we would want it to be able to invoke clang-cl directly, so I guess that does necessitate it *not* being under llvm.
> On Thu, Sep 7, 2017 at 11:26 AM David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> wrote:
> It's used, but not a huge repository of things, as you can see. I think I've run it once or twice, but a long time ago. It was introduced for/by Apple/LLDB stuff, so it's not something I've paid much attention to.
> It's probably not suitable as part of llvm tests directly. Those tests are designed to be shorter/narrower/more focussed than full integration tests (we don't execute any compiled programs under test there, for example).
> Porting to lit seems probably fine/good.
> On Thu, Sep 7, 2017 at 11:23 AM Zachary Turner <zturner at google.com <mailto:zturner at google.com>> wrote:
> What is the status of debuginfo-tests? Is it actively supported? How do you run it? It doesn't appear to be based on lit, any particular reason? Why is it its own repo instead of being part of llvm repo?
> Anything I should be aware of / careful of when messing around in here? And any reason it can't be moved to llvm/tests and ported to lit?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev