llvm-project/clang/test/CodeCompletion/macros-in-modules.c

// RUN: rm -rf %t && mkdir %t
// RUN: echo 'module Foo { header "foo.h" }' > %t/module.modulemap
// RUN: echo '#define FOO_MACRO 42' > %t/foo.h
// RUN: c-index-test -code-completion-at=%s:%(line+5):1 -I %t %s | FileCheck %s
// RUN: c-index-test -code-completion-at=%s:%(line+4):1 -I %t -fmodules -fmodules-cache-path=%t %s | FileCheck %s

#include "foo.h"
int x =
/*here*/1;

// CHECK: FOO_MACRO
[Preprocessor] Iterating over all macros should include those from modules. So, iterate over the list of macros mentioned in modules, and make sure those are in the master table. This isn't particularly efficient, but hopefully it's something that isn't done too often. PR23929 and rdar://problem/21480635 llvm-svn: 240571 2015-06-24 19:27:02 +00:00			`// RUN: rm -rf %t && mkdir %t`
			`// RUN: echo 'module Foo { header "foo.h" }' > %t/module.modulemap`
			`// RUN: echo '#define FOO_MACRO 42' > %t/foo.h`
[lit] Script to automate use of %(line-n). Use in CodeComplete tests. Tests where the RUN-lines/CHECK-ed output refer to line numbers in the test file are a maintenance burden, as inserting text in the appropriate place invalidates all the subsequent line numbers. Lit supports %(line+n) for this, and FileCheck supports [[@LINE+N]]. But many existing tests don't make use of it and still need to be modified. This commit adds a script that can find line numbers in tests according to a regex and replace them with the appropriate relative-line reference. It contains some options to avoid inappropriately rewriting tests where absolute numbers are appropriate: a "nearby" threshold and a refusal by default to replace only some matched line numbers. I've applied it to CodeComplete tests, this proves the concept but also are the single worst group of tests I've seen in this respect. These changes are likely to hit merge conflicts, but can be regenerated with: ``` find ../clang/test/CodeCompletion/ -type f \| grep -v /Inputs/ \| xargs ../llvm/utils/relative_lines.py --verbose --near=20 --pattern='-code-completion-at[ =]%s:(\\d+):' --pattern='requires fix-it: {(\d+):\d+-(\d+):\d+}' ```` As requested in https://reviews.llvm.org/D140044 Fixes https://github.com/llvm/llvm-project/issues/59553 Differential Revision: https://reviews.llvm.org/D140217 2022-12-16 15:59:11 +01:00			`// RUN: c-index-test -code-completion-at=%s:%(line+5):1 -I %t %s \| FileCheck %s`
			`// RUN: c-index-test -code-completion-at=%s:%(line+4):1 -I %t -fmodules -fmodules-cache-path=%t %s \| FileCheck %s`
[Preprocessor] Iterating over all macros should include those from modules. So, iterate over the list of macros mentioned in modules, and make sure those are in the master table. This isn't particularly efficient, but hopefully it's something that isn't done too often. PR23929 and rdar://problem/21480635 llvm-svn: 240571 2015-06-24 19:27:02 +00:00
			`#include "foo.h"`
			`int x =`
			`/here/1;`

			`// CHECK: FOO_MACRO`