The NetBSD Project

CVS log for src/tests/usr.bin/xlint/lint1/Attic/msg_161.exp

[BACK] Up to [cvs.NetBSD.org] / src / tests / usr.bin / xlint / lint1

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.9, Fri Jun 17 20:23:59 2022 UTC (7 months, 2 weeks ago) by rillig
Branch: MAIN
CVS Tags: HEAD
Changes since 1.8: +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.8 / (download) - annotate - [select for diffs], Thu Jun 16 16:58:36 2022 UTC (7 months, 3 weeks ago) by rillig
Branch: MAIN
Changes since 1.7: +10 -10 lines
Diff to previous 1.7 (colored)

tests/lint: make expectation lines in the tests more detailed

This commit migrates msg_100 until msg_199.

Revision 1.7 / (download) - annotate - [select for diffs], Sat Apr 16 20:57:10 2022 UTC (9 months, 3 weeks ago) by rillig
Branch: MAIN
Changes since 1.6: +6 -0 lines
Diff to previous 1.6 (colored)

lint: investigate why lint only warns about some constant conditions

Noticed in lex.c, in the macro kwdef, where lint complains about the
condition containing '||' but not about the conditions containing only
'>' or '=='.

Revision 1.6 / (download) - annotate - [select for diffs], Sun Mar 21 15:44:57 2021 UTC (22 months, 2 weeks 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.5: +1 -0 lines
Diff to previous 1.5 (colored)

lint: fix reachability for while (0)

Revision 1.5 / (download) - annotate - [select for diffs], Sun Feb 28 03:59:28 2021 UTC (23 months, 1 week ago) by rillig
Branch: MAIN
Changes since 1.4: +0 -2 lines
Diff to previous 1.4 (colored)

lint: do not warn about constant expressions involving sizeof

These expressions are indeed constant for a specific platform, but on
another platform their value may change.  This makes them unsuspicious
and legitimate for portable code.

Seen in rump_syscalls.c, as 'sizeof(int) > sizeof(register_t)'.

Revision 1.4 / (download) - annotate - [select for diffs], Sun Feb 28 03:29:12 2021 UTC (23 months, 1 week ago) by rillig
Branch: MAIN
Changes since 1.3: +2 -0 lines
Diff to previous 1.3 (colored)

tests/lint: add test for constant expression involving sizeof

Revision 1.3 / (download) - annotate - [select for diffs], Sun Jan 31 12:44:34 2021 UTC (2 years ago) by rillig
Branch: MAIN
Changes since 1.2: +0 -1 lines
Diff to previous 1.2 (colored)

lint: don't warn about constant condition in 'do { } while (0)'

Revision 1.2 / (download) - annotate - [select for diffs], Sun Jan 31 12:29:16 2021 UTC (2 years ago) by rillig
Branch: MAIN
Changes since 1.1: +4 -1 lines
Diff to previous 1.1 (colored)

lint: add tests for 'constant in conditional context'

One of these tests explains why 'do { } while (0)' is so usual that
there is no reason to warn about it.  That warning will not survive for
long.

Revision 1.1 / (download) - annotate - [select for diffs], Sat Jan 2 10:22:43 2021 UTC (2 years, 1 month 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.

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.




CVSweb <webmaster@jp.NetBSD.org>