<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/clang/test/Import, 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-12-06T02:35:08+00:00</updated>
<entry>
<title>Tighten up CHECK lines added in a9f10ebffa to work on ARM.</title>
<updated>2019-12-06T02:35:08+00:00</updated>
<author>
<name>Douglas Yung</name>
<email>douglas.yung@sony.com</email>
</author>
<published>2019-12-06T02:35:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=757bc55f8314c8c789f81b7f0b3397a8c6148b68'/>
<id>urn:sha1:757bc55f8314c8c789f81b7f0b3397a8c6148b68</id>
<content type='text'>
On ARM platforms, the compiler generates an additional line containing `-CXXRecordDecl which is not the intended line, but preceeds the intended match causing the test to fail.
</content>
</entry>
<entry>
<title>[ASTImporter] Various source location and range import fixes.</title>
<updated>2019-12-05T16:44:13+00:00</updated>
<author>
<name>Balázs Kéri</name>
<email>1.int32@gmail.com</email>
</author>
<published>2019-12-05T15:21:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a9f10ebffaa29e009081faa2720f8ea9bb356658'/>
<id>urn:sha1:a9f10ebffaa29e009081faa2720f8ea9bb356658</id>
<content type='text'>
Summary:
ASTImporter contained wrong or missing imports of SourceLocation
and SourceRange for some objects. At least a part of such errors
is fixed now.
Source location import fixes in namespace, enum, record,
class template specialization declarations and DeclRefExpr,
UnresolvedLookupExpr, UnresolvedMemberExpr, NestedNameSpecifierLoc.

Reviewers: martong, a.sidorin, shafik

Reviewed By: shafik

Subscribers: rnkovacs, dkrupp, Szelethus, gamesh411, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D60499
</content>
</entry>
<entry>
<title>[ASTImporter] Add support for BuiltinTemplateDecl</title>
<updated>2019-10-30T13:53:35+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-10-30T13:50:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=ba7bde65dcfff543cefc1de9adcda7f503ffffde'/>
<id>urn:sha1:ba7bde65dcfff543cefc1de9adcda7f503ffffde</id>
<content type='text'>
Summary:
That decl kind is currently not implemented. BuiltinTemplateDecl is for decls that are hardcoded in the
ASTContext, so we can import them like we do other builtin decls by just taking the equivalent
decl from the target ASTContext.

Reviewers: martong, a.sidorin, shafik

Reviewed By: martong, shafik

Subscribers: rnkovacs, kristina, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D69566
</content>
</entry>
<entry>
<title>[clang] Ignore builtin namespaces in test/Import/cxx-anon-namespace</title>
<updated>2019-10-01T11:53:20+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-10-01T11:53:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=ed5a8971ecff1e8e51ced7f44e3f6bb71fd97086'/>
<id>urn:sha1:ed5a8971ecff1e8e51ced7f44e3f6bb71fd97086</id>
<content type='text'>
Some platforms (e.g. AArch64) put __va_list in the 'std' namespace which might
end up being the first namespace we match in this test. Instead let
the first namespace match via file name/line so that we skip the
builtin namespaces.

llvm-svn: 373327
</content>
</entry>
<entry>
<title>[ASTImporter] Copy Argument Passing Restrictions setting when importing a CXXRecordDecl definition</title>
<updated>2019-04-26T18:51:28+00:00</updated>
<author>
<name>Shafik Yaghmour</name>
<email>syaghmour@apple.com</email>
</author>
<published>2019-04-26T18:51:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=16b90733c751ccf80e2c6e31838dc6f1a4f3d38e'/>
<id>urn:sha1:16b90733c751ccf80e2c6e31838dc6f1a4f3d38e</id>
<content type='text'>
Summary:
For a CXXRecordDecl the RecordDeclBits are stored in the DeclContext. Currently when we import the definition of a CXXRecordDecl via the ASTImporter we do not copy over this data.
This change will add support for copying the ArgPassingRestrictions from RecordDeclBits to fix an LLDB expression parsing bug where we would set it to not pass in registers.
Note, we did not copy over any other of the RecordDeclBits since we don't have tests for those. We know that copying over LoadedFieldsFromExternalStorage would be a error and that may be the case for others as well.

The companion LLDB review: https://reviews.llvm.org/D61146

Differential Review: https://reviews.llvm.org/D61140

llvm-svn: 359338
</content>
</entry>
<entry>
<title>[ASTImporter] Fix importing OperatorDelete from CXXConstructorDecl</title>
<updated>2019-01-22T17:59:45+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-01-22T17:59:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=1c5d23f1405994da05697b3b66c9f5a32735fdc3'/>
<id>urn:sha1:1c5d23f1405994da05697b3b66c9f5a32735fdc3</id>
<content type='text'>
Summary:
Shafik found out that importing a CXXConstructorDecl will create a translation unit that
causes Clang's CodeGen to crash. The reason for that is that we don't copy the OperatorDelete
from the CXXConstructorDecl when importing. This patch fixes it and adds a test case for that.

Reviewers: shafik, martong, a_sidorin, a.sidorin

Reviewed By: martong, a_sidorin

Subscribers: rnkovacs, cfe-commits

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

llvm-svn: 351849
</content>
</entry>
<entry>
<title>[ASTImporter] Add test for importing anonymous namespaces.</title>
<updated>2019-01-21T10:14:31+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-01-21T10:14:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4e4c0664f9b4c65e344317239b66271a67a800ad'/>
<id>urn:sha1:4e4c0664f9b4c65e344317239b66271a67a800ad</id>
<content type='text'>
Reviewers: a.sidorin, a_sidorin

Reviewed By: a_sidorin

Subscribers: a_sidorin, martong, cfe-commits

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

llvm-svn: 351739
</content>
</entry>
<entry>
<title>[AST] Store "UsesADL" information in CallExpr.</title>
<updated>2018-12-12T21:50:55+00:00</updated>
<author>
<name>Eric Fiselier</name>
<email>eric@efcs.ca</email>
</author>
<published>2018-12-12T21:50:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5cdc2cda28ac86ba4ec3771341545355452fdc86'/>
<id>urn:sha1:5cdc2cda28ac86ba4ec3771341545355452fdc86</id>
<content type='text'>
Summary:
Currently the Clang AST doesn't store information about how the callee of a CallExpr was found. Specifically if it was found using ADL.

However, this information is invaluable to tooling. Consider a tool which renames usages of a function. If the originally CallExpr was formed using ADL, then the tooling may need to additionally qualify the replacement.
Without information about how the callee was found, the tooling is left scratching it's head. Additionally, we want to be able to match ADL calls as quickly as possible, which means avoiding computing the answer on the fly.

This patch changes `CallExpr` to store whether it's callee was found using ADL. It does not change the size of any AST nodes.


Reviewers: fowles, rsmith, klimek, shafik

Reviewed By: rsmith

Subscribers: aaron.ballman, riccibruno, calabrese, titus, cfe-commits

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

llvm-svn: 348977
</content>
</entry>
<entry>
<title>Compound literals, enums, et al require const expr</title>
<updated>2018-11-09T00:41:36+00:00</updated>
<author>
<name>Bill Wendling</name>
<email>isanbard@gmail.com</email>
</author>
<published>2018-11-09T00:41:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=8003edc9aa0160c777252b6ed8e96fc35f039bd4'/>
<id>urn:sha1:8003edc9aa0160c777252b6ed8e96fc35f039bd4</id>
<content type='text'>
Summary:
Compound literals,  enums, file-scoped arrays, etc. require their
initializers and size specifiers to be constant. Wrap the initializer
expressions in a ConstantExpr so that we can easily check for this later
on.

Reviewers: rsmith, shafik

Reviewed By: rsmith

Subscribers: cfe-commits, jyknight, nickdesaulniers

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

llvm-svn: 346455
</content>
</entry>
<entry>
<title>[AST] Only store the needed data in WhileStmt</title>
<updated>2018-10-30T13:42:41+00:00</updated>
<author>
<name>Bruno Ricci</name>
<email>riccibrun@gmail.com</email>
</author>
<published>2018-10-30T13:42:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=bacf751add8304789a452fc01c78e73771c8d72e'/>
<id>urn:sha1:bacf751add8304789a452fc01c78e73771c8d72e</id>
<content type='text'>
Don't store the data for the condition variable if not needed.
This cuts the size of WhileStmt by up to a pointer.
The order of the children is kept the same.

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

Reviewed By: rjmccall

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