#
1.9 |
|
12-Sep-2023 |
rillig |
lint: mark unreachable function call arguments as used as well
Previously, in a '?:' expression with a constant condition, the branch that is not taken was skipped but any identifiers in there were intended to be marked as used. In function call expressions, this only worked for the last argument, as the PUSH operator is not a binary operator (see ops.def). Cover this case as well.
|
#
1.8 |
|
12-Sep-2023 |
rillig |
lint: mark symbols that are only used in untaken '?:' branch as used
|
#
1.7 |
|
12-Sep-2023 |
rillig |
tests/lint: show that '?:' skips untaken branches early
This is probably done to avoid wrong warnings from branches that are only taken on other platforms, but it also generates a wrong 'unused' warning.
|
#
1.6 |
|
09-Jul-2023 |
rillig |
lint: clean up wording in diagnostics
Use the term 'parameter' as defined in C99 3.15.
|
#
1.5 |
|
07-Jul-2023 |
rillig |
lint: warn about function definitions without header declaration
The existing warning was only issued for function declarations, not for function definitions.
The interesting change in the tests is in msg_351.c. Many other tests use non-static functions due to their syntactic brevity. In these tests, the warning is disabled individually, to allow new functions to be added without generating warning 351.
|
Revision tags: netbsd-10-base
|
#
1.4 |
|
16-Jun-2022 |
rillig |
tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
|
#
1.3 |
|
09-Apr-2021 |
rillig |
lint: quote placeholders in messages for unused variables
|
#
1.2 |
|
30-Jan-2021 |
rillig |
lint: remove message 189, add tests for a few other messages
Message 189 would have applied to traditional C and was supposed to detect assignments between struct and union types. The corresponding check had never been implemented though.
Traditional C has been superseded for 30 years now, therefore there is no point in adding this check retroactively.
|
#
1.1 |
|
02-Jan-2021 |
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.
|
#
1.9 |
|
12-Sep-2023 |
rillig |
lint: mark unreachable function call arguments as used as well
Previously, in a '?:' expression with a constant condition, the branch that is not taken was skipped but any identifiers in there were intended to be marked as used. In function call expressions, this only worked for the last argument, as the PUSH operator is not a binary operator (see ops.def). Cover this case as well.
|
#
1.8 |
|
12-Sep-2023 |
rillig |
lint: mark symbols that are only used in untaken '?:' branch as used
|
#
1.7 |
|
12-Sep-2023 |
rillig |
tests/lint: show that '?:' skips untaken branches early
This is probably done to avoid wrong warnings from branches that are only taken on other platforms, but it also generates a wrong 'unused' warning.
|
#
1.6 |
|
09-Jul-2023 |
rillig |
lint: clean up wording in diagnostics
Use the term 'parameter' as defined in C99 3.15.
|
#
1.5 |
|
07-Jul-2023 |
rillig |
lint: warn about function definitions without header declaration
The existing warning was only issued for function declarations, not for function definitions.
The interesting change in the tests is in msg_351.c. Many other tests use non-static functions due to their syntactic brevity. In these tests, the warning is disabled individually, to allow new functions to be added without generating warning 351.
|
Revision tags: netbsd-10-base
|
#
1.4 |
|
16-Jun-2022 |
rillig |
tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
|
#
1.3 |
|
09-Apr-2021 |
rillig |
lint: quote placeholders in messages for unused variables
|
#
1.2 |
|
30-Jan-2021 |
rillig |
lint: remove message 189, add tests for a few other messages
Message 189 would have applied to traditional C and was supposed to detect assignments between struct and union types. The corresponding check had never been implemented though.
Traditional C has been superseded for 30 years now, therefore there is no point in adding this check retroactively.
|
#
1.1 |
|
02-Jan-2021 |
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.
|
#
1.6 |
|
09-Jul-2023 |
rillig |
lint: clean up wording in diagnostics
Use the term 'parameter' as defined in C99 3.15.
|
#
1.5 |
|
07-Jul-2023 |
rillig |
lint: warn about function definitions without header declaration
The existing warning was only issued for function declarations, not for function definitions.
The interesting change in the tests is in msg_351.c. Many other tests use non-static functions due to their syntactic brevity. In these tests, the warning is disabled individually, to allow new functions to be added without generating warning 351.
|
Revision tags: netbsd-10-base
|
#
1.4 |
|
16-Jun-2022 |
rillig |
tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
|
#
1.3 |
|
09-Apr-2021 |
rillig |
lint: quote placeholders in messages for unused variables
|
#
1.2 |
|
30-Jan-2021 |
rillig |
lint: remove message 189, add tests for a few other messages
Message 189 would have applied to traditional C and was supposed to detect assignments between struct and union types. The corresponding check had never been implemented though.
Traditional C has been superseded for 30 years now, therefore there is no point in adding this check retroactively.
|
#
1.1 |
|
02-Jan-2021 |
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.
|
#
1.5 |
|
07-Jul-2023 |
rillig |
lint: warn about function definitions without header declaration
The existing warning was only issued for function declarations, not for function definitions.
The interesting change in the tests is in msg_351.c. Many other tests use non-static functions due to their syntactic brevity. In these tests, the warning is disabled individually, to allow new functions to be added without generating warning 351.
|
Revision tags: netbsd-10-base
|
#
1.4 |
|
16-Jun-2022 |
rillig |
tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
|
#
1.3 |
|
09-Apr-2021 |
rillig |
lint: quote placeholders in messages for unused variables
|
#
1.2 |
|
30-Jan-2021 |
rillig |
lint: remove message 189, add tests for a few other messages
Message 189 would have applied to traditional C and was supposed to detect assignments between struct and union types. The corresponding check had never been implemented though.
Traditional C has been superseded for 30 years now, therefore there is no point in adding this check retroactively.
|
#
1.1 |
|
02-Jan-2021 |
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.
|
#
1.4 |
|
16-Jun-2022 |
rillig |
tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
|
#
1.3 |
|
09-Apr-2021 |
rillig |
lint: quote placeholders in messages for unused variables
|
#
1.2 |
|
30-Jan-2021 |
rillig |
lint: remove message 189, add tests for a few other messages
Message 189 would have applied to traditional C and was supposed to detect assignments between struct and union types. The corresponding check had never been implemented though.
Traditional C has been superseded for 30 years now, therefore there is no point in adding this check retroactively.
|
#
1.1 |
|
02-Jan-2021 |
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.
|
#
1.3 |
|
09-Apr-2021 |
rillig |
lint: quote placeholders in messages for unused variables
|
#
1.2 |
|
30-Jan-2021 |
rillig |
lint: remove message 189, add tests for a few other messages
Message 189 would have applied to traditional C and was supposed to detect assignments between struct and union types. The corresponding check had never been implemented though.
Traditional C has been superseded for 30 years now, therefore there is no point in adding this check retroactively.
|
#
1.1 |
|
02-Jan-2021 |
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.
|