| History log of /src/tests/usr.bin/xlint/lint1/msg_117.c |
| Revision | | Date | Author | Comments |
| 1.16 |
| 14-Sep-2025 |
rillig | lint: warn about signed '<<' that ends up exactly in the msb
|
| 1.15 |
| 14-Sep-2025 |
rillig | lint: add more type details to several messages
In most expressions, the integer promotions are performed on the
operands, making the actual type different from the "visible" type of an
operand. To properly explain the situation, mention the type before the
integer promotions in case it differs from the resulting type.
|
| 1.14 |
| 07-Jul-2023 |
rillig | lint: warn about function definitions without header declaration
The existing warning was only issued for function declarations, not for
function definitions.
The interesting change in the tests is in msg_351.c. Many other tests
use non-static functions due to their syntactic brevity. In these
tests, the warning is disabled individually, to allow new functions to
be added without generating warning 351.
|
| 1.13 |
| 29-Jan-2023 |
rillig | lint: don't warn about negative '>>' when the actual value is positive
|
| 1.12 |
| 29-Jan-2023 |
rillig | tests/lint: merge tests for '>>'
|
| 1.11 |
| 16-Jun-2022 |
rillig | tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
| 1.10 |
| 04-Sep-2021 |
rillig | tests/lint: provide more background information on signed '>>'
|
| 1.9 |
| 27-Aug-2021 |
rillig | tests/lint: document correct lint warnings for '>>'
The previous commit contained wrong assumptions. Upon closer
inspection, the lint warning is correct.
|
| 1.8 |
| 27-Aug-2021 |
rillig | tests/lint: test wrong warning for bitwise '>>'
Seen in /usr/include/netbt/hci.h, function hci_filter_set.
|
| 1.7 |
| 15-Aug-2021 |
rillig | lint: fix wrong warning about 'unsigned char >> constant'
|
| 1.6 |
| 15-Aug-2021 |
rillig | tests/lint: demonstrate wrong warning about signed '>>'
Seen in libdes/ostr2key.c(81).
|
| 1.5 |
| 05-Apr-2021 |
rillig | tests/lint: one comment per expected diagnostic
This makes it possible to check for diagnostics that contain commas.
|
| 1.4 |
| 31-Jan-2021 |
rillig | lint: mention the operator in messages about bit shifts
|
| 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 |
| 09-Jan-2021 |
rillig | lint: add tests for messages 117, 120, 125, 127
|
| 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.
|
