| History log of /src/tests/usr.bin/xlint/lint1/msg_035.c |
| Revision | | Date | Author | Comments |
| 1.12 |
| 12-Apr-2025 |
rillig | lint: s/illegal/invalid/g
Lint does not provide legal advice.
|
| 1.11 |
| 15-Jun-2022 |
rillig | branches: 1.11.4;
tests/lint: replace 'expect' comments with 'expect+-' comments
The 'expect+-' comments provide more context, which makes it easier to
read the .c files on their own, without having to look up the actual
diagnostics in the .exp files.
Add tests for messages 105 and 106, which were about the obscure feature
of some traditional C compilers that allowed the expression 'x->member'
to access a struct member, even if 'x' had integer type.
The remaining tests will be migrated in a future commit.
|
| 1.10 |
| 22-Dec-2021 |
rillig | lint: use C90 instead of C89 when referring to the C standard
|
| 1.9 |
| 02-May-2021 |
rillig | tests/lint: add test for bit-field types in GCC mode
|
| 1.8 |
| 05-Apr-2021 |
rillig | tests/lint: one comment per expected diagnostic
This makes it possible to check for diagnostics that contain commas.
|
| 1.7 |
| 28-Feb-2021 |
rillig | lint: add type information to 'illegal bit-field type'
|
| 1.6 |
| 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.5 |
| 02-Jan-2021 |
rillig | lint: fix message 308 "Invalid type for _Complex"
Previously, lint aborted since it didn't expect tspec_name to be called
with NOTSPEC, which at that point was the only possible value of
dcs->d_cmod.
|
| 1.4 |
| 02-Jan-2021 |
rillig | lint: allow _Bool for bit-fields
|
| 1.3 |
| 02-Jan-2021 |
rillig | lint: fix and document test for illegal bit-fields
The _Complex bit-field should have been commented out.
|
| 1.2 |
| 02-Jan-2021 |
rillig | lint: add test for message 35: illegal bit-field type
Bug: _Bool is not accepted as a bit-field, but it should be.
Bug: lint aborts in a controlled manner with message "common/tyname.c,
190: tspec_name(0)" when it sees a declaration of a _Complex bit-field.
(Not that a _Complex bit-field would make any sense.)
|
| 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.
|
| 1.11.4.1 |
| 02-Aug-2025 |
perseant | Sync with HEAD
|
