forked from OSchip/llvm-project
b5f8171a1b
When a '>>' token is split into two '>' tokens (in C++11 onwards), or (as an extension) when we do the same for other tokens starting with a '>', we can't just use a location pointing to the first '>' as the location of the split token, because that would result in our miscomputing the length and spelling for the token. As a consequence, for example, a refactoring replacing 'A<X>' with something else would sometimes replace one character too many, and similarly diagnostics highlighting a template-id source range would highlight one character too many. Fix this by creating an expansion range covering the first character of the '>>' token, whose spelling is '>'. For this to work, we generalize the expansion range of a macro FileID to be either a token range (the common case) or a character range (used in this new case). llvm-svn: 331155 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| ParseAST.cpp | ||
| ParseCXXInlineMethods.cpp | ||
| ParseDecl.cpp | ||
| ParseDeclCXX.cpp | ||
| ParseExpr.cpp | ||
| ParseExprCXX.cpp | ||
| ParseInit.cpp | ||
| ParseObjc.cpp | ||
| ParseOpenMP.cpp | ||
| ParsePragma.cpp | ||
| ParseStmt.cpp | ||
| ParseStmtAsm.cpp | ||
| ParseTemplate.cpp | ||
| ParseTentative.cpp | ||
| Parser.cpp | ||