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

[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, 2016, at 11:22 AM, Ed Maste via lldb-dev <lldb-dev at lists.llvm.org> wrote:
> 
> 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
> (lang/cpp/unicode-literals/TestUnicodeLiterals.py)
> UNEXPECTED SUCCESS: test_expr2_dwarf
> (lang/cpp/unicode-literals/TestUnicodeLiterals.py)
> UNEXPECTED SUCCESS: test_expr3_dwarf
> (lang/cpp/unicode-literals/TestUnicodeLiterals.py)
> 
> The example in the test case works as expected:
> 
> (lldb) expr L"Hello"
> (const wchar_t [6]) $0 = L"Hello"
> 
> Are these passing on Linux as well?
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev