Hi all,
I've recently taken over maintenance of my company's llvm+lldb branch,
where we have added support for our in-house architecture (in llvm) as well
as support for debugging through both hardware and our simulator. Our llvm
fork is public/open source, however many of our runtime libraries an
Hi Adam,
I think the best idea is to comment on the commit on Phabricator (
reviews.llvm.org ) as it seems to be a relatively recent change. Otherwise if
you can somehow provide way to reproduce the deadlock using only code you can
share + LLVM.org sources then filing a bug would be an option t
> On Jun 22, 2021, at 10:10 AM, Adam HARRIES via lldb-dev
> wrote:
>
> Hi all,
>
> I've recently taken over maintenance of my company's llvm+lldb branch, where
> we have added support for our in-house architecture (in llvm) as well as
> support for debugging through both hardware and our s
On Mon, Jun 21, 2021 at 3:53 PM Chris Lattner via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> On Jun 9, 2021, at 10:50 AM, Philip Reames via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
>
> Specific to the dev lists, I'm very hesitant about moving from mailing
> lists to discourse. Why?
>
> Well,
https://bugs.llvm.org/show_bug.cgi?id=39166
Apoorv Sachan changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |apoorv.99.sac...@gmail.com
--
You are receivin
