| History log of /src/tests/usr.bin/xlint/lint1/msg_142.c |
| Revision | | Date | Author | Comments |
| 1.12 |
| 08-Jun-2024 |
rillig | tests/lint: remove unused lint1-skip-if selector
|
| 1.11 |
| 09-Jul-2023 |
rillig | lint: clean up the wording of a few diagnostics
|
| 1.10 |
| 11-Apr-2023 |
rillig | lint: don't wrongly warn about overflow in complex constants
Seen in lib/libm.
|
| 1.9 |
| 10-Apr-2023 |
rillig | tests/lint: demonstrate wrong warning with complex numbers
|
| 1.8 |
| 28-Mar-2023 |
rillig | lint: warn about extern declarations outside headers
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
|
| 1.7 |
| 22-Jun-2022 |
rillig | lint: add quotes around placeholders for the remaining messages
Reword some of the messages slightly, exchanging brevity for clarity.
Message 138 is kept as-is, as it is not yet covered by any tests.
Message 240 is kep as-is, as it is unreachable.
|
| 1.6 |
| 21-Aug-2021 |
rillig | tests/lint: guard against typos in test environment configuration
Some tests had "lint1-only-if" without a trailing colon, others included
the trailing colon. The tests that included the trailing colon were run
even though they were supposed to be skipped, and they failed, as could
be expected.
To prevent further typos, always require the trailing colon, just as in
"lint1-flags" and fail fast on unknown "lint1" comments.
|
| 1.5 |
| 13-Jul-2021 |
rillig | tests/lint: skip test for floating point overflow on alpha
On alpha and a few other platforms (see t_integration.sh), 'long double'
has 128 bit, which under IEEE 754 rules means a decimal exponent of up
to 4932.
|
| 1.4 |
| 05-Apr-2021 |
rillig | tests/lint: one comment per expected diagnostic
This makes it possible to check for diagnostics that contain commas.
|
| 1.3 |
| 31-Jan-2021 |
rillig | lint: add expections to tests
msg_098: fix suffix for floating point constant
msg_127: remove prototype
msg_146: fix return type
|
| 1.2 |
| 08-Jan-2021 |
rillig | lint: add tests for several messages
|
| 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.
|
