| #
e83db15a |
| 20-Feb-2021 |
rillig <rillig@NetBSD.org> |
lint: clean up some of the C99 tests
Several C99 tests do not actually test C99 features but instead GCC
features. All these tests should be double-checked again.
In some other tests, split the in
lint: clean up some of the C99 tests
Several C99 tests do not actually test C99 features but instead GCC
features. All these tests should be double-checked again.
In some other tests, split the initializers into more lines, which makes
it easier to read the debug log corresponding to these tests. This will
be necessary for reworking the initializer code to actually conform to
C99.
show more ...
|
| #
70a1a91e |
| 31-Jan-2021 |
rillig <rillig@NetBSD.org> |
lint: format tests in a common style
The lint tests do not focus on the whitespace since that is the most
boring part of code style. Therefore, format the tests to be readable
by following share/mi
lint: format tests in a common style
The lint tests do not focus on the whitespace since that is the most
boring part of code style. Therefore, format the tests to be readable
by following share/misc/style as close as possible.
show more ...
|
| #
aadcb6a6 |
| 31-Jan-2021 |
rillig <rillig@NetBSD.org> |
lint: add common header for all tests
For those tests that didn't use GCC-style line markers such as "# 2",
the line numbers of the diagnostics stay the same. This is purely
conincidental. Before,
lint: add common header for all tests
For those tests that didn't use GCC-style line markers such as "# 2",
the line numbers of the diagnostics stay the same. This is purely
conincidental. Before, the 3 lines came from lint's built-in
definitions (see 'builtins' in main1.c), and line number counting
continued as if nothing had happened, making the first line of the
actual file line 4. These 3 built-in lines are now replaced with 3
lines of file header.
show more ...
|