Up to [cvs.NetBSD.org] / src / tests / usr.bin / xlint / lint1
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.4, Fri Jun 17 20:23:59 2022 UTC (7 months, 3 weeks ago) by rillig
CVS Tags: HEAD
Changes since 1.3: +0 -0 lines
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.3 / (download) - annotate - [select for diffs], Tue Apr 19 22:14:30 2022 UTC (9 months, 2 weeks ago) by rillig
Changes since 1.2: +1 -1 lines
Diff to previous 1.2 (colored)
lint: only warn about unsigned constants in C90 migration mode For C99 code, the difference between traditional C and C90 is not relevant. Seen in sqlite3.c line 30448.
Revision 1.2 / (download) - annotate - [select for diffs], Tue Mar 16 23:39:41 2021 UTC (22 months, 3 weeks ago) by rillig
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)
tests/lint: add tests for a few more messages
Revision 1.1 / (download) - annotate - [select for diffs], Sat Jan 2 10:22:43 2021 UTC (2 years, 1 month ago) by 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.
This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.