summaryrefslogtreecommitdiffstats
path: root/llvm/docs/CommandGuide/FileCheck.rst
diff options
context:
space:
mode:
authorReid Kleckner <rnk@google.com>2016-12-09 21:10:43 +0000
committerReid Kleckner <rnk@google.com>2016-12-09 21:10:43 +0000
commit6c03cfb091c5550e6e4630946498c2271eaa471d (patch)
tree9dff44e0503c4b9c8566ee0dcd32ef613ff17285 /llvm/docs/CommandGuide/FileCheck.rst
parent5869b5a4471f90490e1f16f5f1dea3a4d0b41ff3 (diff)
downloadbcm5719-llvm-6c03cfb091c5550e6e4630946498c2271eaa471d.tar.gz
bcm5719-llvm-6c03cfb091c5550e6e4630946498c2271eaa471d.zip
Remove special error recovery for ::(id)
The code pattern used to implement the token rewriting hack doesn't interact well with token caching in the pre-processor. As a result, clang would crash on 'int f(::(id));' while doing a tenative parse of the contents of the outer parentheses. The original code from PR11852 still doesn't crash the compiler. This error recovery also often does the wrong thing with member function pointers. The test case from the original PR doesn't recover the right way either: void S::(*pf)() = S::f; // should be 'void (S::*pf)()' Instead we were recovering as 'void S::*pf()', which is still wrong. If we still think that users mistakenly parenthesize identifiers in nested name specifiers, we should change clang to intentionally parse that form with an error, rather than doing a token rewrite. Fixes PR26623, but I think there will be many more bugs like this around token rewriting in the parser. Reviewers: rsmith, rtrieu Differential Revision: https://reviews.llvm.org/D25882 llvm-svn: 289273
Diffstat (limited to 'llvm/docs/CommandGuide/FileCheck.rst')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud