![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / src / tests / usr.bin / xlint / lint1
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.13, Fri Jun 17 20:23:59 2022 UTC (7 months, 2 weeks ago) by rillig
Branch: MAIN
CVS Tags: HEAD
Changes since 1.12: +0 -0
lines
FILE REMOVED
tests/lint: remove .exp files, as they have become redundant Now that each lint1 test lists all generated diagnostics as 'expect' comments, the information from the .exp files is no longer needed. The only information that gets lost is the order of the diagnostics, which is mostly relevant for paired messages like 'inconsistent definition' + 'previous definition was here'.
Revision 1.12 / (download) - annotate - [select for diffs], Fri Apr 1 22:28:21 2022 UTC (9 months, 4 weeks ago) by rillig
Branch: MAIN
Changes since 1.11: +1 -1
lines
Diff to previous 1.11 (colored)
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.
Revision 1.11 / (download) - annotate - [select for diffs], Sun Aug 29 17:01:27 2021 UTC (17 months ago) by rillig
Branch: MAIN
Changes since 1.10: +1 -1
lines
Diff to previous 1.10 (colored)
lint: in C99 mode, make implicit function declarations an error In tree.c 1.294 from 2021-06-28, I had already tried this, but at that time, there were too many implicit function definitions in the NetBSD tree. Most of them were GCC builtins, which lint did not recognize. Therefore I had to revert to a warning in tree.c 1.302 from 2021-06-30. In the meantime, lint has learnt to recognize compiler builtins, see is_compiler_builtin, so try again now. The build logs from x86_64, i386, sparc and sparc64 show no more implicit function declarations.
Revision 1.10 / (download) - annotate - [select for diffs], Wed Jun 30 14:32:41 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.9: +1 -1
lines
Diff to previous 1.9 (colored)
lint: in C99 mode, only warn about implicit function declarations Since tree.c 1.294 from 2021-06-28 (two days ago), lint errored out on an implicit function declaration. In principle it is correct to do so since C99 requires it, but in practice there are a several functions that are not declared in the translation unit itself since they are provided by the compiler. Typical examples for GCC and Clang are the various functions named '__builtin_*' and '__atomic_*'. For now, only warn about these but don't error out.
Revision 1.9 / (download) - annotate - [select for diffs], Wed Jun 30 14:23:50 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.8: +7 -7
lines
Diff to previous 1.8 (colored)
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.
Revision 1.8 / (download) - annotate - [select for diffs], Wed Jun 30 12:26:35 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.7: +4 -0
lines
Diff to previous 1.7 (colored)
tests/lint: add test for type name of enum converted to int
Revision 1.7 / (download) - annotate - [select for diffs], Mon Jun 28 11:27:00 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.6: +3 -2
lines
Diff to previous 1.6 (colored)
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".
Revision 1.6 / (download) - annotate - [select for diffs], Mon Jun 28 11:09:35 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.5: +3 -3
lines
Diff to previous 1.5 (colored)
lint: fix parse error for type 'void (*)[*]'
Revision 1.5 / (download) - annotate - [select for diffs], Mon Jun 28 10:29:05 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.4: +2 -2
lines
Diff to previous 1.4 (colored)
lint: fix type name for prototype function without parameters
Revision 1.4 / (download) - annotate - [select for diffs], Mon Jun 28 10:23:50 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.3: +6 -6
lines
Diff to previous 1.3 (colored)
lint: add type information to message 155 (type mismatch)
Revision 1.3 / (download) - annotate - [select for diffs], Mon Jun 28 10:07:43 2021 UTC (19 months ago) by rillig
Branch: MAIN
Changes since 1.2: +7 -1
lines
Diff to previous 1.2 (colored)
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.
Revision 1.2 / (download) - annotate - [select for diffs], Sun Mar 21 20:45:00 2021 UTC (22 months, 1 week ago) by rillig
Branch: MAIN
CVS Tags: cjep_sun2x-base1,
cjep_sun2x-base,
cjep_sun2x,
cjep_staticlib_x-base1,
cjep_staticlib_x-base,
cjep_staticlib_x
Changes since 1.1: +1 -1
lines
Diff to previous 1.1 (colored)
lint: prefix error messages with 'error:' This makes it easier to find these errors in the build logs.
Revision 1.1 / (download) - annotate - [select for diffs], Sat Jan 2 10:22:43 2021 UTC (2 years ago) by rillig
Branch: MAIN
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.