From: Argyrios Kyrtzidis Date: Fri, 22 Feb 2013 22:28:58 +0000 (+0000) Subject: [libclang] Fix assertion hit when code-completing inside a function macro with more X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fb70380f2f4d546c5ac37bb5bb98ad2c46810c41;p=platform%2Fupstream%2Fllvm.git [libclang] Fix assertion hit when code-completing inside a function macro with more arguments than it should accept. llvm-svn: 175925 --- diff --git a/clang/lib/Lex/PPMacroExpansion.cpp b/clang/lib/Lex/PPMacroExpansion.cpp index 3e68fbd..99ab134 100644 --- a/clang/lib/Lex/PPMacroExpansion.cpp +++ b/clang/lib/Lex/PPMacroExpansion.cpp @@ -620,8 +620,10 @@ MacroArgs *Preprocessor::ReadFunctionLikeMacroArgs(Token &MacroName, EOFTok.setLength(0); ArgTokens.push_back(EOFTok); ++NumActuals; - assert(NumFixedArgsLeft != 0 && "Too many arguments parsed"); - --NumFixedArgsLeft; + if (!ContainsCodeCompletionTok || NumFixedArgsLeft != 0) { + assert(NumFixedArgsLeft != 0 && "Too many arguments parsed"); + --NumFixedArgsLeft; + } } // Okay, we either found the r_paren. Check to see if we parsed too few diff --git a/clang/test/Index/complete-macro-args.c b/clang/test/Index/complete-macro-args.c index 0b4dd20..2507984 100644 --- a/clang/test/Index/complete-macro-args.c +++ b/clang/test/Index/complete-macro-args.c @@ -19,6 +19,11 @@ void test2(struct Point *p) { MACRO3(p->x } +#define FM(x) x +void test3(struct Point *p) { + FM(p->x, a); +} + #define VGM(...) 0 #define VGM2(...) __VA_ARGS__ @@ -37,6 +42,7 @@ void test3(struct Point *p) { // RUN: c-index-test -code-completion-at=%s:12:12 %s | FileCheck %s // RUN: c-index-test -code-completion-at=%s:18:13 %s | FileCheck %s // RUN: c-index-test -code-completion-at=%s:19:13 %s | FileCheck %s +// RUN: c-index-test -code-completion-at=%s:24:9 %s | FileCheck %s // CHECK: FieldDecl:{ResultType float}{TypedText x} (35) // CHECK-NEXT: FieldDecl:{ResultType float}{TypedText y} (35) // CHECK-NEXT: FieldDecl:{ResultType float}{TypedText z} (35) @@ -46,7 +52,7 @@ void test3(struct Point *p) { // With these, code-completion is unknown because the macro argument (and the // completion point) is not expanded by the macro definition. -// RUN: c-index-test -code-completion-at=%s:28:15 %s -DEOF_TEST1 | FileCheck %s -check-prefix=CHECK-EOF -// RUN: c-index-test -code-completion-at=%s:32:20 %s -DEOF_TEST2 | FileCheck %s -check-prefix=CHECK-EOF +// RUN: c-index-test -code-completion-at=%s:33:15 %s -DEOF_TEST1 | FileCheck %s -check-prefix=CHECK-EOF +// RUN: c-index-test -code-completion-at=%s:37:20 %s -DEOF_TEST2 | FileCheck %s -check-prefix=CHECK-EOF // CHECK-EOF: Completion contexts: // CHECK-EOF: Unknown