I added the VLA support to clang and lldb about a year ago, so you'll need
fairly recent version of both for it to work.
-- adrian
> On Feb 17, 2020, at 12:25 PM, Levo DeLellis wrote:
>
> It looks like I wasn't careful and mixed version. I compiled with clang-9 but
> used lldb-6. Surprisingly
It looks like I wasn't careful and mixed version. I compiled with clang-9
but used lldb-6. Surprisingly this was the only error I notice when mixing
these version. I could swear I tried compiling with clang-6. I'd double
check but it appears that installing lldb-9 removed lldb(-6) from my system
Th
On Thu, 2020-02-13 at 23:34 +0100, Hans Wennborg via Release-testers
wrote:
> Hello everyone,
>
> Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It
> includes 98 commits since the previous release candidate.
>
This time I've switched to python3.8, and I've noticed that libc+
That is interesting. According to LLDB's test/lang/c/vla/* frame variable for a
VLA is supposed to work. Frame variable is also supposed to hide the
__vla_expr0 artificial helper variable. Is this an older LLDB from your system
or an LLDB you built from source? If yes, would you mind filing a bu
Thanks! Added this and the other binaries I've gotten so far to the
release page and github.
On Sat, Feb 15, 2020 at 6:25 PM Brian Cain wrote:
>
> Uploaded ubuntu 18 binaries.
>
> $ cat clang+llvm-10.0.0-rc2-x86_64-linux-gnu-ubuntu-18.04.tar.xz.sha256
> 8ca2cd0e0ba2243c095134373b46ccad822192b0495
On Thu, Feb 13, 2020 at 11:34 PM Hans Wennborg wrote:
>
> Hello everyone,
>
> Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It
> includes 98 commits since the previous release candidate.
>
> Source code and docs are available at
> https://prereleases.llvm.org/10.0.0/#rc2 and
