<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/packages/Python/lldbsuite/test/expression_command/pr35310, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2019-09-01T09:12:37+00:00</updated>
<entry>
<title>[lldb] Restructure test folders to match LLDB command hierarchy</title>
<updated>2019-09-01T09:12:37+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-09-01T09:12:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=29872606d220420d53fde7cc5e3bea15f8da62e7'/>
<id>urn:sha1:29872606d220420d53fde7cc5e3bea15f8da62e7</id>
<content type='text'>
Summary:
As discussed on lldb-dev, this patch moves some LLDB tests into a hierarchy that more closely
resembles the commands we use in the LLDB interpreter. This patch should only move tests
that use the command interpreter and shouldn't touch any tests that primarily test the SB API.

Reviewers: #lldb, jfb, JDevlieghere

Reviewed By: #lldb, JDevlieghere

Subscribers: dexonsmith, arphaman, JDevlieghere, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D67033

llvm-svn: 370605
</content>
</entry>
<entry>
<title>[lldbsuite] Un-xfail tests on Windows that are now passing (pt.2)</title>
<updated>2018-12-19T19:10:25+00:00</updated>
<author>
<name>Stella Stamenova</name>
<email>stilis@microsoft.com</email>
</author>
<published>2018-12-19T19:10:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=0ab990345a7e8314cd4819363a40e52a83d53ac5'/>
<id>urn:sha1:0ab990345a7e8314cd4819363a40e52a83d53ac5</id>
<content type='text'>
This is a set of tests that were all marked as failing becuse of pr21765. The bug is not fixed (as in more of the tests that were marked this way are failing), but this set is passing. It is possible that some of them are false positives, but there's a large number of unexpectedly passing tests on Windows, so I am doing a bulk un-xfail to get the buildbot to green.

llvm-svn: 349668
</content>
</entry>
<entry>
<title>Fix whitespace in the python test suite.</title>
<updated>2018-07-27T22:20:59+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2018-07-27T22:20:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=23d7a9ebbe6fd815af1f7263197df701c784d012'/>
<id>urn:sha1:23d7a9ebbe6fd815af1f7263197df701c784d012</id>
<content type='text'>
Summary:
The test suite has often unnecessary trailing whitespace, and sometimes
unnecessary trailing lines or a missing final new line. This patch just strips
trailing whitespace/lines and adds missing newlines at the end.

Subscribers: ki.stfu, JDevlieghere, christof, lldb-commits

Differential Revision: https://reviews.llvm.org/D49943

llvm-svn: 338171
</content>
</entry>
<entry>
<title>[lit, lldbsuite] Disable tests that are failing because of pr21765 and pr24489</title>
<updated>2018-05-17T16:58:00+00:00</updated>
<author>
<name>Stella Stamenova</name>
<email>stilis@microsoft.com</email>
</author>
<published>2018-05-17T16:58:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3e79551700883a926bb606b9e78c403779329bef'/>
<id>urn:sha1:3e79551700883a926bb606b9e78c403779329bef</id>
<content type='text'>
Summary: These three tests are failing on Windows and looking into the failures, they could be mapped to pr21765 and pr24489

Reviewers: asmith, labath, zturner

Reviewed By: zturner

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D47018

llvm-svn: 332629
</content>
</entry>
<entry>
<title>Use the DWARF linkage name when importing C++ methods.</title>
<updated>2018-03-27T19:40:50+00:00</updated>
<author>
<name>Davide Italiano</name>
<email>davide@freebsd.org</email>
</author>
<published>2018-03-27T19:40:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=675767a5910d2ec77ef8b51c78fe312cf9022896'/>
<id>urn:sha1:675767a5910d2ec77ef8b51c78fe312cf9022896</id>
<content type='text'>
When importing C++ methods into clang AST nodes from the DWARF symbol
table, preserve the DW_AT_linkage_name and use it as the linker
("asm") name for the symbol.

Concretely, this enables `expression` to call into names that use the
GNU `abi_tag` extension, and enables lldb to call into code using
std::string or std::list from recent versions of libstdc++. See
https://bugs.llvm.org/show_bug.cgi?id=35310 . It also seems broadly
more robust than relying on the DWARF-&gt;clang-&gt;codegen pipeline to
roundtrip properly, but I'm not immediately aware of any other cases
in which it makes a difference.

Patch by Nelson Elhage!

Differential Revision:  https://reviews.llvm.org/D40283

llvm-svn: 328658
</content>
</entry>
</feed>
