Up to [cvs.NetBSD.org] / src / tests / usr.bin / xlint / lint1
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.8, Fri Jun 17 20:23:58 2022 UTC (7 months, 2 weeks ago) by rillig
CVS Tags: HEAD
Changes since 1.7: +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.7 / (download) - annotate - [select for diffs], Thu May 12 00:18:35 2022 UTC (8 months, 3 weeks ago) by rillig
Changes since 1.6: +4 -5 lines
Diff to previous 1.6 (colored)
lint: fix support for __alignof__, add support for __alignof Broken since lex.c 1.129 from yesterday.
Revision 1.6 / (download) - annotate - [select for diffs], Thu May 12 00:09:44 2022 UTC (8 months, 3 weeks ago) by rillig
Changes since 1.5: +5 -4 lines
Diff to previous 1.5 (colored)
tests/lint: adjust tests to reflect missing support of __alignof__ The change in lex.c 1.129 attempted to add support for __alignof, in addition to the existing support for __alignof__. It failed by removing support for __alignof__, while allowing the plain 'alignof' instead.
Revision 1.5 / (download) - annotate - [select for diffs], Sat Apr 2 21:47:04 2022 UTC (10 months ago) by rillig
Changes since 1.4: +4 -2 lines
Diff to previous 1.4 (colored)
lint: remove unreachable message 'compiler takes alignment of function'
Revision 1.4 / (download) - annotate - [select for diffs], Fri Apr 1 23:16:32 2022 UTC (10 months ago) by rillig
Changes since 1.3: +1 -1 lines
Diff to previous 1.3 (colored)
lint: add type details to message about 'sizeof(function)' The code in add_function is severely broken, it mixes up the return type of the function with the argument types. For now, at least show the guessed type in the diagnostic, to allow human readers quickly spot the bug. Extend the test cases in decl_direct_abstract.c to show that the behavior differs unreasonably if the first parameter of the function is equal to its return type.
Revision 1.3 / (download) - annotate - [select for diffs], Thu Aug 26 19:23:25 2021 UTC (17 months, 1 week ago) by rillig
Changes since 1.2: +2 -1 lines
Diff to previous 1.2 (colored)
tests/lint: add tests for several messages
Revision 1.2 / (download) - annotate - [select for diffs], Sun Mar 21 20:44:59 2021 UTC (22 months, 1 week 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)
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, 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.