On 6/21/21 12:53 PM, Chris Lattner wrote:
On Jun 9, 2021, at 10:50 AM, Philip Reames via llvm-dev
mailto:llvm-...@lists.llvm.org>> wrote:
Specific to the dev lists, I'm very hesitant about moving from
mailing lists to discourse. Why?
Well, the first and most basic is I'm worried about havi
On Wed, 23 Jun 2021 at 13:59, Tobias Hieta via llvm-dev <
llvm-...@lists.llvm.org> wrote:
> I am very active in the Discord and try my best to help people and
> while I often refer people to post to the mailing list if they can't
> find an answer, I have never and never seen anyone direct new peop
Hi Greg,
Thanks for the advice!
> [...] I would suggest just submitting a bug and attaching stack traces of
your deadlock. Loading a core file is very similar across all targets, so I
can't imagine this being hard to reproduce with another core file?
Glad to hear this - I'll do so soon then. I a
Hi Raphael,
Thanks for the advice!
> 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
On Wed, Jun 23, 2021 at 12:51 AM Chris Lattner via cfe-dev
wrote:
>
> On Jun 22, 2021, at 6:01 PM, James Y Knight wrote:
>
> On Mon, Jun 21, 2021 at 3:53 PM Chris Lattner via cfe-dev
> wrote:
>>
>> On Jun 9, 2021, at 10:50 AM, Philip Reames via llvm-dev
>> wrote:
>>
>> Specific to the dev lis
https://bugs.llvm.org/show_bug.cgi?id=50814
Bug ID: 50814
Summary: Several tests fail with GCC as LLDB can't properly
call constructors from expressions
Product: lldb
Version: unspecified
Hardware: PC
OS: Li
