| History log of /src/tests/usr.bin/xlint/lint1/msg_155.c |
| Revision | | Date | Author | Comments |
| 1.12 |
| 28-Mar-2023 |
rillig | lint: warn about extern declarations outside headers
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
|
| 1.11 |
| 17-Jun-2022 |
rillig | tests/lint: make 'expect+-' comments stricter
Previously, the expectations from these comments were already satisfied
if the expectation occurred somewhere in the actual message from lint.
This meant that the prefix 'error:' or 'warning:' could be omitted from
the 'expect' comment. These omissions were hard to see in a manual
review. Now any omissions must be visually marked with '...'.
The test msg_342 now reports its messages properly as being in the file
msg_342.c, rather than msg_341.c. This had been a copy-and-paste
mistake.
|
| 1.10 |
| 01-Apr-2022 |
rillig | lint: improve determination of abstract typename
Still not perfect, but at least a step in the right direction. See
decl_direct_abstract.c for the missing edge cases.
See PR#22119.
|
| 1.9 |
| 30-Jun-2021 |
rillig | lint: mention the name of an implicitly declared function
In the regular NetBSD builds, this happened in swab.c:65. That line
contains __predict_false, which may or may not be a macro. In other
cases, there may be more than one function call in a single line.
|
| 1.8 |
| 30-Jun-2021 |
rillig | tests/lint: add test for type name of enum converted to int
|
| 1.7 |
| 28-Jun-2021 |
rillig | lint: in C99 mode, complain about implicitly declared functions
C99, foreword, p5, item 22 lists among the major changes from C90:
"remove implicit function declaration".
|
| 1.6 |
| 28-Jun-2021 |
rillig | lint: fix parse error for type 'void (*)[*]'
|
| 1.5 |
| 28-Jun-2021 |
rillig | lint: fix type name for prototype function without parameters
|
| 1.4 |
| 28-Jun-2021 |
rillig | lint: add type information to message 155 (type mismatch)
|
| 1.3 |
| 28-Jun-2021 |
rillig | lint: turn null pointer dereference into assertion failure
Originally I only needed a message that would output the type name from
an abstract-declarator (C99 6.7.6), to see whether lint interprets the
types correctly.
Message 155 looked like a good candidate, but it only revealed more
incomplete and untested code in lint.
|
| 1.2 |
| 21-Feb-2021 |
rillig | lint: force each test to declare the expected diagnostics
By listing the expected diagnostics directly at the code that triggers
the diagnostics, it is easier to cross-check whether the diagnostics
make sense.
No functional change to lint itself.
|
| 1.1 |
| 02-Jan-2021 |
rillig | lint: add a test for each message produced by lint1
Having a test for each message ensures that upcoming refactorings don't
break the basic functionality. Adding the tests will also discover
previously unknown bugs in lint.
The tests ensure that every lint message can actually be triggered, and
they demonstrate how to do so. Having a separate file for each test
leaves enough space for documenting historical anecdotes, rationale or
edge cases, keeping them away from the source code.
The interesting details of this commit are in Makefile and
t_integration.sh. All other files are just auto-generated.
When running the tests as part of ATF, they are packed together as a
single test case. Conceptually, it would have been better to have each
test as a separate test case, but ATF quickly becomes very slow as soon
as a test program defines too many test cases, and 50 is already too
many. The time complexity is O(n^2), not O(n) as one would expect.
It's the same problem as in tests/usr.bin/make, which has over 300 test
cases as well.
|
