Re: [lldb-dev] Details on rdar://18684408?

2016-02-19 Thread Pavel Labath via lldb-dev
Linux is ok as well. I've enabled the tests everywhere except windows. Please add your arch back if you notice problems. pl On 18 February 2016 at 19:37, Zachary Turner via lldb-dev wrote: > Does not work on Windows yet, so please leave it xfail'ed on windows for now >

Re: [lldb-dev] Details on rdar://18684408?

2016-02-18 Thread Zachary Turner via lldb-dev
Does not work on Windows yet, so please leave it xfail'ed on windows for now On Thu, Feb 18, 2016 at 11:30 AM Sean Callanan via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I apologize for this confusion. I recently fixed these as a side effect > of some major changes in IRForTarget.cpp. >

Re: [lldb-dev] Details on rdar://18684408?

2016-02-18 Thread Sean Callanan via lldb-dev
I apologize for this confusion. I recently fixed these as a side effect of some major changes in IRForTarget.cpp. These should be fixed on pretty much all platforms, and the expectedFailure can be removed. If they’re passing on Linux too, let’s remove the expectedFailure. Sean > On Feb 18,

[lldb-dev] Details on rdar://18684408?

2016-02-18 Thread Ed Maste via lldb-dev
The tests in lang/cpp/unicode-literals/TestUnicodeLiterals.py are marked with @unittest2.expectedFailure("rdar://18684408"). These tests are passing on FreeBSD: UNEXPECTED SUCCESS: test_and_run_command_dwarf (lang/c/const_variables/TestConstVariables.py) UNEXPECTED SUCCESS: test_expr1_dwarf