| 0e2c34f92f00628d48968dfea096d36381f494cb |
|
23-Mar-2015 |
Stephen Hines <srhines@google.com> |
Update aosp/master clang for rebase to r230699.
Change-Id: I6a546ab3d4ae37119eebb735e102cca4f80ab520
/external/clang/test/Parser/recovery.cpp
|
| 6bcf27bb9a4b5c3f79cb44c0e4654a6d7619ad89 |
|
29-May-2014 |
Stephen Hines <srhines@google.com> |
Update Clang for 3.5 rebase (r209713).
Change-Id: I8c9133b0f8f776dc915f270b60f94962e771bc83
/external/clang/test/Parser/recovery.cpp
|
| 651f13cea278ec967336033dd032faef0e9fc2ec |
|
24-Apr-2014 |
Stephen Hines <srhines@google.com> |
Updated to Clang 3.5a.
Change-Id: I8127eb568f674c2e72635b639a3295381fe8af82
/external/clang/test/Parser/recovery.cpp
|
| e78e8fc27140309092fb56d77a72f31fa085f9da |
|
23-Dec-2013 |
Bill Wendling <isanbard@gmail.com> |
---Merging r196453
Parse: Recover better from bad definitions with base specifiers
We would skip until the next comma, hoping good things whould lie there,
however this would fail when we have such things as this:
struct A {};
template <typename>
struct D;
template <>
struct D<C> : B, A::D;
Once this happens, we would believe that D with a nested namespace
specifier of A was a variable that was being declared. We would go on
to complain that there was an extraneous 'template <>' on their variable
declaration.
Crashes would happen when 'A' gets defined as 'enum class A {}' as
various asserts would fire.
Instead, we should skip up until the semicolon if we see that we are in
the middle of a definition and the current token is a ':'
This fixes PR17084.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/branches/release_34@197905 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| f0cc19f43d5e05dbd22d00faca8c093b7005be3f |
|
19-Nov-2013 |
Bill Wendling <isanbard@gmail.com> |
Merging r195163:
------------------------------------------------------------------------
r195163 | rsmith | 2013-11-19 14:47:36 -0800 (Tue, 19 Nov 2013) | 5 lines
PR9547: If we're parsing a simple-declaration that contains a tag definition,
and we see an ill-formed declarator that would probably be well-formed if the
tag definition were just missing a semicolon, use that as the diagnostic
instead of producing some other mysterious error.
------------------------------------------------------------------------
git-svn-id: https://llvm.org/svn/llvm-project/cfe/branches/release_34@195165 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| 7faf81ff1dc8f8dc724e928ba90ccbfad0fdc2bc |
|
16-Nov-2013 |
Richard Smith <richard-llvm@metafoo.co.uk> |
PR17949: Fix crash if someone puts a namespace inside a class template.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@194872 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| b310439121c875937d78cc49cc969bc1197fc025 |
|
09-Nov-2013 |
Richard Smith <richard-llvm@metafoo.co.uk> |
Try to recover a bit better if a close brace is missing from the end of a class
definition. If we see something that looks like a namespace definition inside a
class, that strongly indicates that a close brace was missing somewhere.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@194319 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| 2d67097ad41f4c2fe82ebce3f587e06498f1bd71 |
|
17-Aug-2013 |
Richard Smith <richard-llvm@metafoo.co.uk> |
Refactor all diagnosing of TypoCorrections through a common function, in
preparation for teaching this function how to diagnose a correction that
includes importing a module.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@188602 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| 37ec8d589c5de34d0e260f0599395519bd7498de |
|
05-Dec-2012 |
Richard Smith <richard-llvm@metafoo.co.uk> |
In C++, if we hit an error in the class-head, don't try to parse the class body.
Our error recovery path may have made the class anonymous, and that has a pretty
disastrous impact on any attempt to parse a class body containing constructors.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@169374 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| a0d5878b7e1c54551c0445354788e4259900c03c |
|
25-Oct-2012 |
David Tweed <david.tweed@arm.com> |
Correct test inovocations to use %clang_cc1 rather than direct invocation (so that it can have additional options set when trying to debug issues causing regressions).
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@166681 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| 53aec2a2770afc242c70fd88975cd0ea389087c0 |
|
25-Oct-2012 |
Richard Smith <richard-llvm@metafoo.co.uk> |
'constexpr' and 'friend' are both declaration specifiers. Teach the parser this, for better error recovery.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@166645 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| 50dc12ad05d4a3a57e83852756498afce4307a77 |
|
16-Jun-2012 |
Kaelyn Uhrain <rikka@google.com> |
Recover when correcting an unknown type name to a keyword like "struct".
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@158573 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|
| 994d73f8473cb2cd3ce2f69c9575c95015be788a |
|
11-Apr-2012 |
Richard Smith <richard-llvm@metafoo.co.uk> |
Part of PR10101: after a parse error in a declaration, try harder to find the
right place to pick up parsing. In C++, this had a tendency to skip everything
declared within headers if the TU starts with garbage.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@154530 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Parser/recovery.cpp
|