| History log of /src/tests/usr.bin/xlint/lint1/emit.exp-ln |
| Revision | | Date | Author | Comments |
| 1.15 |
| 09-Jun-2024 |
rillig | lint: fix usage marker for nested function calls
|
| 1.14 |
| 09-Jun-2024 |
rillig | tests/lint: demonstrate wrong result for nested function calls
|
| 1.13 |
| 22-May-2023 |
rillig | tests/lint1: allow whitespace in files containing the expected output
This reduces the amount of wizardry needed to interpret the files. For
a more gentle introduction of the file format, see ../lint2/msg_000.ln.
The whitespace that is removed is very similar to the one in the lint2
tests, the difference is that '%<space>' and '%#' need to be preserved
in abbreviated printf and scanf format strings.
|
| 1.12 |
| 22-May-2023 |
rillig | lint: fix emitted type for arrays of unknown size
|
| 1.11 |
| 22-May-2023 |
rillig | tests/lint: demonstrate wrong emitted array length in initialization
Seen in usr.bin/indent/debug.c, in the various 'name' arrays.
|
| 1.10 |
| 15-Jan-2022 |
rillig | tests/lint: expect complete messages in feature tests
Previously, the tests contained many comments like /* expect: 123 */,
which were useless to a casual reader since nobody is expected to learn
lint's message IDs by heart. Replace these with the complete
diagnostics, to show what lint is complaining about.
The tests named msg_*.c have been left unmodified since they mention the
full message text in their header comment.
No functional change.
|
| 1.9 |
| 28-Nov-2021 |
rillig | lint: do not export unnamed objects to the .ln file
Since these objects are unnamed, they cannot be referenced by other
files or even create name clashes.
Seen in usr.sbin/cpuctl/aarch64.c, reported by Christos.
|
| 1.8 |
| 28-Nov-2021 |
rillig | tests/lint1: reproduce parse error for accidentally exported name
Seen in usr.sbin/cpuctl/aarch64.c line 118.
error: aarch64.ln:857:
not alnum or _: (for '118d-1.0d1200000000_tmpA16PcC')
The name 00000000_tmp was not supposed to be exported.
|
| 1.7 |
| 04-Sep-2021 |
rillig | tests/lint: test emitting format strings
|
| 1.6 |
| 30-Aug-2021 |
rillig | tests/lint: test writing and reading .ln files
The test case for reading varargs functions is no longer necessary, the
code is covered by the newly added tests as well.
Test inline function and return value usage.
|
| 1.5 |
| 30-Aug-2021 |
rillig | tests/lint: test varargs, printflike, scanflike
|
| 1.4 |
| 28-Aug-2021 |
rillig | lint: do not emit GCC builtin functions
Lint1 no longer emits declarations of GCC builtin functions and calls to
them.
Previously, lint generated 3421 useless warnings in a default NetBSD
build, like this:
__atomic_load_n, arg 1 used inconsistently
acl.c(216)[pointer to unsigned int]
rbtdb.c(921)[pointer to unsigned short]
This was because lint just doesn't understand that these functions are
type-generic, which is indeed unusual in C.
These useless warnings made the lint output more frightening than it
should actually be. Together with the strange formatting of the
diagnostics (space-space-tab after the main message, two spaces and two
colons between the occurrences, symbols are listed in hashcode order),
this creates the impression that lint is not intended to be a
user-friendly tool.
For now, fix the excess warnings, leaving the other items for later.
|
| 1.3 |
| 28-Aug-2021 |
rillig | tests/lint: demonstrate that GCC builtins are emitted by default
They will be skipped in a follow-up commit, but to see the effects of
that, they first need to be emitted.
|
| 1.2 |
| 08-Aug-2021 |
rillig | tests/lint: test passing of printf-like strings between lint1 and lint2
|
| 1.1 |
| 27-Jun-2021 |
rillig | tests/lint: rename expected .ln file to .exp-ln
This way, the hack for suffixes is no longer needed.
|
