Re: [lldb-dev] Some API test failures are really opaque/could be improved

2021-10-25 Thread David Blaikie via lldb-dev
On Mon, Oct 25, 2021 at 1:28 PM Louis Dionne wrote: > I believe the issue is probably not related so much to > LLVM_ENABLE_PROJECTS vs LLVM_ENABLE_RUNTIMES, but rather to the fact that > LLVM_ENABLE_RUNTIMES uses per-target runtime directories now (hasn't always > been the case), which basically

Re: [lldb-dev] Some API test failures are really opaque/could be improved

2021-10-25 Thread Louis Dionne via lldb-dev
I believe the issue is probably not related so much to LLVM_ENABLE_PROJECTS vs LLVM_ENABLE_RUNTIMES, but rather to the fact that LLVM_ENABLE_RUNTIMES uses per-target runtime directories now (hasn't always been the case), which basically means that libc++ ends up in `/lib//libc++.so` instead of

Re: [lldb-dev] Some API test failures are really opaque/could be improved

2021-10-25 Thread David Blaikie via lldb-dev
+Louis Dionne - perhaps the libcxx and lldb folks would be interesting in finding a suitable way to address this issue, since currently either option (using libcxx in ENABLE_PROJECTS or using it in ENABLE_RUNTIMES) is incomplete - if I use ENABLE_RUNTIMES I get the libcxx testing run against the j

Re: [lldb-dev] [llvm-dev] Upstream an LLDB language plugin for D and support of custom expressions

2021-10-25 Thread David Blaikie via lldb-dev
+lldb-dev On Mon, Oct 25, 2021 at 9:36 AM Luís Ferreira via llvm-dev < llvm-...@lists.llvm.org> wrote: > Hi llvm-dev, > > I'm writing here to discuss the addition of D language plugin to LLDB. > Following the issue #52223 from Bugzilla, we are currently using C/C++ > language plugin for D. This p