Displaying 2 results from an estimated 2 matches for "bad_func".
Did you mean:
load_func
2020 Jul 17
3
[FileCheck] RFC: Add support for line anchors.
...able names aside from
the fact it can't start with '$'.
- When referring to an anchor in a check use the same numeric
variable syntax that FileCheck already supports:
`CHECK: [[#ANCHOR_NAME]][[#ANCHOR_NAME+1]]`
Here is a brief (contrived) example of the usage of this:
```
#define BAD_FUNCTION() badFunction() // LINE-ANCHOR: BAD_FUNC
// Further down in the file
BAD_FUNCTION();
CHECK-NOTES: [[@LINE-1]]:3: warning: called a bad function
CHECK-NOTES :[[#BAD-FUNC]]:3: note: expanded from macro 'BAD_FUNCTION'
```
Regards,
Nathan James
2020 Jul 17
2
[cfe-dev] [FileCheck] RFC: Add support for line anchors.
...; number that where they were defined.
>
> I think something like this could be useful. However, I think it
> would be more useful to have a general directive for defining
> FileCheck variables inline without trying to capture from input. For
> example:
>
> ```
> #define BAD_FUNCTION() badFunction() // CHECK-DEFINE:
> [[#BAD_FUNC:@LINE]]
> // Further down in the file
> BAD_FUNCTION();
> CHECK-NOTES: [[@LINE-1]]:3: warning: called a bad function
> CHECK-NOTES :[[#BAD_FUNC]]:3: note: expanded from macro
> 'BAD_FUNCTION'
> ```
>
> The exac...