Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-03-19T09:19:04+00:00 2020-03-19T09:19:04+00:00 Saar Raz saar@raz.email 2020-03-16T23:43:29+00:00 urn:sha1:35627038123b5b391a20e9f4d44a85c7a325027b TryAnnotateTypeConstraint could annotate a template-id which doesn't end up being a type-constraint, in which case control flow would incorrectly flow into ParseImplicitInt. Reenter the loop in this case. Enable relevant tests for C++20. This required disabling typo-correction during TryAnnotateTypeConstraint and changing a test case which is broken due to a separate bug (will be reported and handled separately). (cherry picked from commit 19fccc52ff2c1da1f93d9317c34769bd9bab8ac8) 2020-03-18T08:35:07+00:00 Hans Wennborg hans@chromium.org 2020-03-18T08:35:07+00:00 urn:sha1:26c762df6c48ae6bb66f76ab7e7e97bbc922ae03 We're not planning more release candidates for 10.0.0 at the moment, so reverting for now. This reverts commit 135744ce689569e7c64033bb5812572d3000239b. 2020-03-17T05:49:42+00:00 Saar Raz saar@raz.email 2020-03-16T23:43:29+00:00 urn:sha1:135744ce689569e7c64033bb5812572d3000239b TryAnnotateTypeConstraint could annotate a template-id which doesn't end up being a type-constraint, in which case control flow would incorrectly flow into ParseImplicitInt. Reenter the loop in this case. Enable relevant tests for C++20. This required disabling typo-correction during TryAnnotateTypeConstraint and changing a test case which is broken due to a separate bug (will be reported and handled separately). (cherry picked from commit 19fccc52ff2c1da1f93d9317c34769bd9bab8ac8) 2020-03-12T11:10:24+00:00 Richard Smith richard@metafoo.co.uk 2020-03-10T00:34:33+00:00 urn:sha1:d9bd6e3c1943e03b783f11d9f2e224ff83f83a7b a dependent context. This matches the GCC behavior. We track the enclosing template depth when determining whether a statement expression is within a dependent context; there doesn't appear to be any other reliable way to determine this. We previously assumed they were neither value- nor instantiation-dependent under any circumstances, which would lead to crashes and other misbehavior. (cherry picked from commit 5c845c1c50ac89a6f12557d1571678f3d1432478) 2020-03-12T11:09:37+00:00 Hans Wennborg hans@chromium.org 2020-03-12T11:09:37+00:00 urn:sha1:5e062819d5adeb2526f1b8393edf5a265bef1591 This turned out to cause problems, and was reverted on master together with its follow-up change in 66addf8e803618758457e4d578c5084e322ca448. This reverts commit 3a843031a5ad83a00d2603f623881cb2b2bf719d. 2020-03-04T08:20:30+00:00 Richard Smith richard@metafoo.co.uk 2020-03-03T23:19:13+00:00 urn:sha1:3a843031a5ad83a00d2603f623881cb2b2bf719d dependent contexts. We previously assumed they were neither value- nor instantiation-dependent under any circumstances, which would lead to crashes and other misbehavior. (cherry picked from commit bdad0a1b79273733df9acc1be4e992fa5d70ec56) 2020-02-12T14:27:14+00:00 Saar Raz saar@raz.email 2020-02-12T14:23:55+00:00 urn:sha1:6f692404a30d7f58b20d40f7a6ceaf826320b145 If an error had occurred when annotating a scope spec during the tentative parse for a type-requirement, we would not revert nor commit the tentative parse, triggerring an assertion failure. Commit the TPA in this case and then do error recovery. (cherry picked from commit 271e495399170d69627c1acd591c9298cb0b5b4b) 2020-01-31T18:10:43+00:00 Saar Raz saar@raz.email 2020-01-31T18:05:09+00:00 urn:sha1:8be11623043c54cc42d7d0a7fac7408efce4ef41 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) 2020-01-31T01:43:48+00:00 Richard Smith richard@metafoo.co.uk 2020-01-31T01:42:17+00:00 urn:sha1:0ce7ea7c6e0e6fde5c961a574592bdd2ebebdeb7 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) 2020-01-26T18:49:23+00:00 Saar Raz saar@raz.email 2020-01-26T18:39:44+00:00 urn:sha1:73a91477f7045d1325570f28e349dd87d9bff49c 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)