<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/clang/test/Parser, 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>2020-06-10T09:46:53+00:00</updated>
<entry>
<title>[clang] Fix crash on visiting null nestedNameSpecifier.</title>
<updated>2020-06-10T09:46:53+00:00</updated>
<author>
<name>Haojian Wu</name>
<email>hokein.wu@gmail.com</email>
</author>
<published>2020-03-17T20:39:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3f4a753f597357db77fe395561234a50daa451b3'/>
<id>urn:sha1:3f4a753f597357db77fe395561234a50daa451b3</id>
<content type='text'>
Summary: Fix https://github.com/clangd/clangd/issues/293

Reviewers: sammccall

Subscribers: ilya-biryukov, kadircet, usaxena95, cfe-commits

Tags: #clang

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

(cherry picked from commit bd763e2cf7c1d84bab95064cc5cbe542b227b025)
</content>
</entry>
<entry>
<title>PR45063: Fix crash on invalid processing an elaborated class template-id</title>
<updated>2020-06-10T09:46:25+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2020-03-14T01:53:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=d942a81c71a3f970857e92e98cc6503b61b589b0'/>
<id>urn:sha1:d942a81c71a3f970857e92e98cc6503b61b589b0</id>
<content type='text'>
with an invalid scope specifier.

(cherry picked from commit 44c3a63c74dddeef17e424ec76bd90c8582d8a3c)
</content>
</entry>
<entry>
<title>Add -std=c++20 flag, replace C++2a with C++20 throughout the Clang</title>
<updated>2020-02-19T21:37:59+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2020-02-19T00:13:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5175565cf154aede57354336102a7f6e15a16a20'/>
<id>urn:sha1:5175565cf154aede57354336102a7f6e15a16a20</id>
<content type='text'>
user interface and documentation, and update __cplusplus for C++20.

WG21 considers the C++20 standard to be finished (even though it still
has some more steps to pass through in the ISO process).

The old flag names are accepted for compatibility, as usual, and we
still have lots of references to C++2a in comments and identifiers;
those can be cleaned up separately.

(cherry picked from commit 24ad121582454e625bdad125c90d9ac0dae948c8)
</content>
</entry>
<entry>
<title>[Concepts] Fix isDeclarationSpecifier to detect type-constraints correctly</title>
<updated>2020-01-31T18:10:43+00:00</updated>
<author>
<name>Saar Raz</name>
<email>saar@raz.email</email>
</author>
<published>2020-01-31T18:05:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=8be11623043c54cc42d7d0a7fac7408efce4ef41'/>
<id>urn:sha1:8be11623043c54cc42d7d0a7fac7408efce4ef41</id>
<content type='text'>
isDeclarationSpecifiers did not handle some cases of placeholder-type-specifiers with
type-constraints, causing parsing bugs in abbreviated constructor templates.

Add comprehensive handling of type-constraints to isDeclarationSpecifier.

(cherry picked from commit b7ce85a130789d23c69156f4b899962458d1f05d)
</content>
</entry>
<entry>
<title>PR41991: Accept attributes on defaulted and deleted friends.</title>
<updated>2020-01-31T01:43:48+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2020-01-31T01:42:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=0ce7ea7c6e0e6fde5c961a574592bdd2ebebdeb7'/>
<id>urn:sha1:0ce7ea7c6e0e6fde5c961a574592bdd2ebebdeb7</id>
<content type='text'>
Attributes are permitted on friend definitions, but we only checked for
a proper function body, not for the =default / =delete cases.

(cherry picked from commit 5ae6554a1dcd2e39346030c06d364492901c9e8d)
</content>
</entry>
<entry>
<title>[Concepts] Fix parsing of scope specifier in compound-requirements, add more tests for scope specifiers in type-constraints</title>
<updated>2020-01-26T18:49:23+00:00</updated>
<author>
<name>Saar Raz</name>
<email>saar@raz.email</email>
</author>
<published>2020-01-26T18:39:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=73a91477f7045d1325570f28e349dd87d9bff49c'/>
<id>urn:sha1:73a91477f7045d1325570f28e349dd87d9bff49c</id>
<content type='text'>
The code for parsing of type-constraints in compound-requirements was not adapted for the new TryAnnotateTypeConstraint which
caused compound-requirements with scope specifiers to ignore them.

Also add regression tests for scope specifiers in type-constraints in more contexts.

(cherry picked from commit 5043962dd3150c6ac72b75174b9460a510d1b5c3)
</content>
</entry>
<entry>
<title>[Concepts] Deprecate -fconcepts-ts, enable Concepts under -std=c++2a</title>
<updated>2020-01-24T00:28:33+00:00</updated>
<author>
<name>Saar Raz</name>
<email>saar@raz.email</email>
</author>
<published>2020-01-23T22:43:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2ec65e229314d468006998eaef7074b86ef7482d'/>
<id>urn:sha1:2ec65e229314d468006998eaef7074b86ef7482d</id>
<content type='text'>
Now with concepts support merged and mostly complete, we do not need -fconcepts-ts
(which was also misleading as we were not implementing the TS) and can enable
concepts features under C++2a. A warning will be generated if users still attempt
to use -fconcepts-ts.

(cherry picked from commit 67c608a9695496cfc9d3fdf9d0b12b554ac6b4df)
</content>
</entry>
<entry>
<title>[Concepts] Placeholder constraints and abbreviated templates</title>
<updated>2020-01-24T00:28:31+00:00</updated>
<author>
<name>Saar Raz</name>
<email>saar@raz.email</email>
</author>
<published>2020-01-22T00:03:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=6a8cd9fc81e86916c1d8d55f52e3c7d5ccdb598a'/>
<id>urn:sha1:6a8cd9fc81e86916c1d8d55f52e3c7d5ccdb598a</id>
<content type='text'>
This patch implements P1141R2 "Yet another approach for constrained declarations".

General strategy for this patch was:

- Expand AutoType to include optional type-constraint, reflecting the wording and easing the integration of constraints.
- Replace autos in parameter type specifiers with invented parameters in GetTypeSpecTypeForDeclarator, using the same logic
  previously used for generic lambdas, now unified with abbreviated templates, by:
  - Tracking the template parameter lists in the Declarator object
  - Tracking the template parameter depth before parsing function declarators (at which point we can match template
    parameters against scope specifiers to know if we have an explicit template parameter list to append invented parameters
    to or not).
- When encountering an AutoType in a parameter context we check a stack of InventedTemplateParameterInfo structures that
  contain the info required to create and accumulate invented template parameters (fields that were already present in
  LambdaScopeInfo, which now inherits from this class and is looked up when an auto is encountered in a lambda context).

Resubmit after fixing MSAN failures caused by incomplete initialization of AutoTypeLocs in TypeSpecLocFiller.

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

(cherry picked from commit b481f028144ca91c15d1db3649ce14f174259e7e)
</content>
</entry>
<entry>
<title>[Concepts] Requires Expressions</title>
<updated>2020-01-24T00:28:22+00:00</updated>
<author>
<name>Saar Raz</name>
<email>saar@raz.email</email>
</author>
<published>2020-01-18T07:11:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=c96ef5118857ff938aa6d304ccf7c0f9b81bc5ba'/>
<id>urn:sha1:c96ef5118857ff938aa6d304ccf7c0f9b81bc5ba</id>
<content type='text'>
Implement support for C++2a requires-expressions.

Re-commit after compilation failure on some platforms due to alignment issues with PointerIntPair.

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

(cherry picked from commit a0f50d731639350c7a79f140f026c27a18215531)
</content>
</entry>
<entry>
<title>Remove redundant CXXScopeSpec from TemplateIdAnnotation.</title>
<updated>2020-01-24T00:28:20+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2020-01-17T23:42:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=ab514b91196345ba4c61026e4997871e85ddd97d'/>
<id>urn:sha1:ab514b91196345ba4c61026e4997871e85ddd97d</id>
<content type='text'>
A TemplateIdAnnotation represents only a template-id, not a
nested-name-specifier plus a template-id. Don't make a redundant copy of
the CXXScopeSpec and store it on the template-id annotation.

This slightly improves error recovery by more properly handling the case
where we would form an invalid CXXScopeSpec while parsing a typename
specifier, instead of accidentally putting the token stream into a
broken "annot_template_id with a scope specifier, but with no preceding
annot_cxxscope token" state.

(cherry picked from commit a42fd84cff265b7e9faa3fe42885ee171393e4db)
</content>
</entry>
</feed>
