aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/validation/test-suite
diff options
authorLuc Van Oostenryck <luc.vanoostenryck@gmail.com>2020-06-25 18:07:18 +0200
committerLuc Van Oostenryck <luc.vanoostenryck@gmail.com>2020-07-04 12:14:26 +0200
commit79a6ae8316377e6b2c043c4d37ed704d86770c3c (patch)
tree27c083475939cb866e2206b9fae0bc2f45bbd68b /validation/test-suite
parentfa15396204a796135f71b5aef6cbbe3ba1fc0eb3 (diff)
downloadsparse-dev-79a6ae8316377e6b2c043c4d37ed704d86770c3c.tar.gz
avoid multiple warnings when inlining undeclared calls
When inlining multiple times a function which contains an undeclared function call, multiple error messages are issued. More annoyingly, only the first one is meaningful, the other ones doesn't even show the incriminated identifier: error: undefined identifier '...' error: not a function <noident> Part of the problem is that the first message is displayed with expression_error() which also sets the expression to &bad_ctype. This change the way how the expression is handled when re-evaluated. Fix this by avoiding the evaluation of function calls that already evaluate to bad_ctype: it's known that an error message have already been issued for them and that nothing good can done with them. Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Diffstat (limited to 'validation/test-suite')
0 files changed, 0 insertions, 0 deletions