On Mon, 25 Mar 2019 19:47:36 +0100, David Zarzycki via lldb-dev wrote:
> Also, given that two of the test failures are Intel specific (the mxcsr
> register write failures), what class of hardware do you use? My workstation
> is Skylake-SP based, if it matters.
OK, I agree it PASSes for me on Haswe
https://bugs.llvm.org/show_bug.cgi?id=41237
Bug ID: 41237
Summary: SIGSEGV on call expression evaluation when debugging
Clang
Product: lldb
Version: 8.0
Hardware: PC
OS: Linux
Status: NEW
> On Mar 26, 2019, at 3:07 AM, Jan Kratochvil wrote:
>
> On Mon, 25 Mar 2019 19:47:36 +0100, David Zarzycki via lldb-dev wrote:
>> Also, given that two of the test failures are Intel specific (the mxcsr
>> register write failures), what class of hardware do you use? My workstation
>> is Skylake-
Hi Raphael,
Any ETA on renaming the variables? The bug you mentioned also had someone offer
to rename the variables in late 2017, but that seemingly never happened.
Thanks!
Dave
> On Mar 25, 2019, at 7:25 AM, Raphael Isemann wrote:
>
> The import-std-module patches are probably just llvm.org/
Yesterday I stumbled upon the initialization code for the "Kalimba"
platform. It looks like this was added in 2014 and never had any tests. If
nobody is relying on this platform, I propose to remove it.
Review: https://reviews.llvm.org/D59850
Thanks,
Jonas
