The NetBSD Project

CVS log for src/tests/usr.bin/xlint/lint1/msg_010.c

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

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.5 / (download) - annotate - [select for diffs], Sat Apr 30 20:24:57 2022 UTC (9 months ago) by rillig
Branch: MAIN
CVS Tags: netbsd-10-base, netbsd-10, HEAD
Changes since 1.4: +7 -4 lines
Diff to previous 1.4 (colored)

lint: document why C11 keywords are available in C99 mode as well

Revision 1.4 / (download) - annotate - [select for diffs], Mon Jan 18 17:43:44 2021 UTC (2 years 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.3: +2 -2 lines
Diff to previous 1.3 (colored)

lint: fix assertion failure for restrict and _Thread_local

Revision 1.3 / (download) - annotate - [select for diffs], Mon Jan 18 17:41:04 2021 UTC (2 years ago) by rillig
Branch: MAIN
Changes since 1.2: +19 -4 lines
Diff to previous 1.2 (colored)

lint: add more test cases for duplicate type qualifiers

Revision 1.2 / (download) - annotate - [select for diffs], Thu Jan 7 18:37:41 2021 UTC (2 years ago) by rillig
Branch: MAIN
Changes since 1.1: +17 -3 lines
Diff to previous 1.1 (colored)

lint: add tests for some messages

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

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>