According to the schedule (e.g. on the right on llvm.org), we should
have tagged the release by now, but we haven't, so we're officially
behind schedule. I'm still optimistic that we can wrap this up pretty
soon, though.
This is what's blocking us:
- PR26509: Crash in InnerLoopVectorizer::vectori
Quoted strings in target.run-args aren't handled correctly.
(lldb) settings set target.run-args "foo bar"
(lldb) settings show target.run-args
target.run-args (array of strings) =
[0]: "foo bar"
This looks correct, but the Args in the ProcessLaunchInfo passed to the
Platform doesn't ha
https://llvm.org/bugs/show_bug.cgi?id=22611
ema...@freebsd.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
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.
> These
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, 201
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/
