History log of /src/tests/usr.bin/xlint/lint1/d_gcc_compound_statements1.c |
Revision | | Date | Author | Comments |
1.14 |
| 02-Jul-2023 |
rillig | lint: allow empty statements in GCC statement expressions
|
1.13 |
| 02-Jul-2023 |
rillig | tests/lint: demonstrate empty statement in GCC statement expression
Seen in external/mit/xorg/lib/dri.old.
|
1.12 |
| 28-Mar-2023 |
rillig | lint: warn about extern declarations outside headers
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
|
1.11 |
| 15-Jun-2022 |
rillig | lint: clean up an empty line and the documentation
No functional change.
|
1.10 |
| 31-May-2022 |
rillig | lint: fix null pointer dereference after syntax error
Found by afl, starting with the malformed input '/**/f=({;/**/};}' that no longer crashes. This input led to 'f=({L:;}', which is at least a syntactically valid prefix of a translation unit, containing a GCC statement expression with an unused label. The error message for this unused label assumed that it would always be inside a function definition.
While here, document incomplete recovery after syntax errors, in msg_249.c.
|
1.9 |
| 24-Apr-2022 |
rillig | lint: error out on declarations with implicit int type
|
1.8 |
| 03-Apr-2022 |
rillig | lint: fix crash after syntax error in GCC statement expression
Since cgram.y 1.226 from 2021-05-03.
|
1.7 |
| 15-Jan-2022 |
rillig | tests/lint: expect complete messages in feature tests
Previously, the tests contained many comments like /* expect: 123 */, which were useless to a casual reader since nobody is expected to learn lint's message IDs by heart. Replace these with the complete diagnostics, to show what lint is complaining about.
The tests named msg_*.c have been left unmodified since they mention the full message text in their header comment.
No functional change.
|
1.6 |
| 20-Jun-2021 |
rillig | lint: fix crash on semantically wrong code in ({...})
Found by afl.
|
1.5 |
| 19-Jun-2021 |
rillig | lint: fix crash in malformed initialization
|
1.4 |
| 27-Mar-2021 |
rillig | tests/lint: move description of tests into the tests themselves
In most cases the descriptions didn't add much to the test name anyway.
|
1.3 |
| 31-Jan-2021 |
rillig | 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.
|
1.2 |
| 31-Jan-2021 |
rillig | 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.
|
1.1 |
| 17-Mar-2012 |
jruoho | branches: 1.1.2; Deprecate tests/util.
|
1.1.2.2 |
| 17-Apr-2012 |
yamt | sync with head
|
1.1.2.1 |
| 17-Mar-2012 |
yamt | file d_gcc_compound_statements1.c was added on branch yamt-pagecache on 2012-04-17 00:09:23 +0000
|