History log of /src/tests/usr.bin/xlint/lint2 |
Revision | Date | Author | Comments |
1.8 | 28-Aug-2021 |
rillig | tests/lint: demonstrate hashcode sorting of the lint2 output
The hashcodes modulo 1009 are:
48 func7000 637 func0000 646 no_prototype 697 func1000 757 func2000 817 func3000 877 func4000 937 func5000 997 func6000
|
1.7 | 24-Aug-2021 |
rillig | lint: allow libraries to use 128-bit integer types
|
1.6 | 08-Aug-2021 |
rillig | tests/lint: include but don't run read_lp64 on 32-bit platforms
The lint1 tests are all in the machine-independent file list, which makes it easier to manage them. At run time, some of them are skipped based on platform characteristics. Do the same for the lint2 tests.
Having the lint2 test named read_lp64 as the only machine-dependent test would complicate things.
The build for i386 had failed because the files for read_lp64 were listed in distrib/sets/lists/tests/mi but were not actually installed.
|
1.5 | 08-Aug-2021 |
rillig | tests/lint: mips64 is not a 64-bit platform
See usr.bin/xlint/arch/mips64/targparam.h.
|
1.4 | 08-Aug-2021 |
rillig | tests/lint: make list of tests simpler
Since the file /usr/tests/usr.bin/xlint/lint2/tests has only been in the file set for a few minutes, it is not marked as obsolete but simply removed.
|
1.3 | 07-Aug-2021 |
rillig | tests/lint: test reading of 128-bit integer types and printf
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add test for reading the lint1 output
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.5 | 04-Sep-2021 |
rillig | tests/lint: test old-style functions in a lint library
To really qualify as old-style, a function must not declare a return type in its definition.
|
1.4 | 04-Sep-2021 |
rillig | tests/lint: test writing of a lint library
The code for that is almost the same as in lint1, but only almost.
|
1.3 | 28-Aug-2021 |
rillig | lint: write the entries for the libraries in alphabetical order
This makes them easier to read by humans.
The checks are still performed in hashcode order since there are no tests that would cover this change.
|
1.2 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.1 | 24-Aug-2021 |
rillig | lint: allow libraries to use 128-bit integer types
|
1.7 | 05-Nov-2024 |
rillig | lint: fix cross references in comments
|
1.6 | 01-Oct-2022 |
rillig | branches: 1.6.4; lint: miscellaneous cleanup
No functional change.
|
1.5 | 15-Jan-2022 |
rillig | tests/lint: fix comments
|
1.4 | 04-Sep-2021 |
rillig | tests/lint: test old-style functions in a lint library
To really qualify as old-style, a function must not declare a return type in its definition.
|
1.3 | 04-Sep-2021 |
rillig | tests/lint: test writing of a lint library
The code for that is almost the same as in lint1, but only almost.
|
1.2 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.1 | 24-Aug-2021 |
rillig | lint: allow libraries to use 128-bit integer types
|
1.6.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 28-Aug-2021 |
rillig | lint: write the entries for the libraries in alphabetical order
This makes them easier to read by humans.
The checks are still performed in hashcode order since there are no tests that would cover this change.
|
1.2 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.1 | 24-Aug-2021 |
rillig | lint: allow libraries to use 128-bit integer types
|
1.2 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.1 | 24-Aug-2021 |
rillig | lint: allow libraries to use 128-bit integer types
|
1.2 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.1 | 05-Aug-2021 |
rillig | branches: 1.1.4; tests/lint: add test skeletons for messages from lint2
|
1.1.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.6 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.5 | 02-Aug-2023 |
rillig | branches: 1.5.2; lint: distinguish between arguments and parameters
|
1.4 | 30-May-2022 |
rillig | lint: clean up comments
No binary change.
|
1.3 | 12-Sep-2021 |
rillig | tests/lint: make documentation for lint2/msg_000 less ambiguous
|
1.2 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.5.2.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.3 | 07-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: add more tests for lint2
|
1.2 | 06-Aug-2021 |
rillig | tests/lint: add tests for declared but unused variables
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.7 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.6 | 14-Jan-2023 |
rillig | branches: 1.6.2; lint: rename lint2 functions to be more expressive
|
1.5 | 01-Oct-2022 |
rillig | lint: miscellaneous cleanup
No functional change.
|
1.4 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.3 | 07-Aug-2021 |
rillig | tests/lint: add more tests for lint2
|
1.2 | 06-Aug-2021 |
rillig | tests/lint: add tests for declared but unused variables
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.6.2.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 06-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add tests for declared but unused variables
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 06-Aug-2021 |
rillig | tests/lint: add tests for declared but unused variables
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 07-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 07-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.5 | 24-May-2025 |
rillig | lint: fix wording in a warning about a type conflict
An object does not have a return type, only functions do.
|
1.4 | 24-May-2025 |
rillig | tests/lint: demonstrate wrong 'object returns' message
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 07-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.5 | 24-May-2025 |
rillig | tests/lint: demonstrate wrong 'object returns' message
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 07-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 30-Nov-2024 |
rillig | tests/lint: test message 7 of lint2
|
1.1 | 05-Aug-2021 |
rillig | branches: 1.1.4; tests/lint: add test skeletons for messages from lint2
|
1.1.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.2 | 30-Nov-2024 |
rillig | tests/lint: test message 7 of lint2
|
1.1 | 05-Aug-2021 |
rillig | branches: 1.1.4; tests/lint: add test skeletons for messages from lint2
|
1.1.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 14-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add tests for messages 8, 9 and 10
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 14-Aug-2021 |
rillig | tests/lint: add tests for messages 8, 9 and 10
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 14-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add tests for messages 8, 9 and 10
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 14-Aug-2021 |
rillig | tests/lint: add tests for messages 8, 9 and 10
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 14-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add tests for messages 8, 9 and 10
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 14-Aug-2021 |
rillig | tests/lint: add tests for messages 8, 9 and 10
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.5 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.4 | 30-Nov-2024 |
rillig | lint: fix type name of prototype function in lint2 messages
Since tyname.c 1.42 from 2021-06-28, when the type names for '(void)' prototypes was fixed for lint1 but not for lint2.
|
1.3 | 30-Nov-2024 |
rillig | tests/lint: demonstrate wrong type name for prototype function
|
1.2 | 07-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.6 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.5 | 30-Nov-2024 |
rillig | lint: fix type name of prototype function in lint2 messages
Since tyname.c 1.42 from 2021-06-28, when the type names for '(void)' prototypes was fixed for lint1 but not for lint2.
|
1.4 | 30-Nov-2024 |
rillig | tests/lint: demonstrate wrong type name for prototype function
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 07-Aug-2021 |
rillig | branches: 1.2.4; tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.4 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.3 | 24-Aug-2021 |
rillig | branches: 1.3.4; tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add more tests for lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 05-Aug-2023 |
rillig | branches: 1.2.2; tests/lint: test C99 printf conversion specifiers in lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.2.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.2 | 05-Aug-2023 |
rillig | branches: 1.2.2; tests/lint: test C99 printf conversion specifiers in lint2
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.2.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.1 | 05-Aug-2021 |
rillig | branches: 1.1.4; tests/lint: add test skeletons for messages from lint2
|
1.1.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.1 | 05-Aug-2021 |
rillig | branches: 1.1.4; tests/lint: add test skeletons for messages from lint2
|
1.1.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.3 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.2 | 01-Apr-2022 |
rillig | branches: 1.2.4; tests/lint2: add missing character in comment
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.1 | 05-Aug-2021 |
rillig | branches: 1.1.4; tests/lint: add test skeletons for messages from lint2
|
1.1.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|
1.2 | 20-Feb-2025 |
rillig | tests/lint: sync messages in test comments with their counterparts
|
1.1 | 05-Aug-2021 |
rillig | branches: 1.1.4; tests/lint: add test skeletons for messages from lint2
|
1.1.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.3 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.2 | 28-Aug-2021 |
rillig | branches: 1.2.4; lint: sort the lint2 diagnostics by symbol name
|
1.1 | 28-Aug-2021 |
rillig | tests/lint: demonstrate hashcode sorting of the lint2 output
The hashcodes modulo 1009 are:
48 func7000 637 func0000 646 no_prototype 697 func1000 757 func2000 817 func3000 877 func4000 937 func5000 997 func6000
|
1.2.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.2 | 15-Jan-2022 |
rillig | tests/lint: fix comments
|
1.1 | 28-Aug-2021 |
rillig | tests/lint: demonstrate hashcode sorting of the lint2 output
The hashcodes modulo 1009 are:
48 func7000 637 func0000 646 no_prototype 697 func1000 757 func2000 817 func3000 877 func4000 937 func5000 997 func6000
|
1.5 | 30-Nov-2024 |
rillig | lint: reword lint2 warnings, reduce punctuation
The previous diagnostics used unusual punctuation, for example by placing spaces inside parentheses, as well as using space-space-tab and double-colon as separators. Convert these diagnostics into readily readable prose, and mark them clearly as coming from lint2, so that they can be related to the tests in /usr/tests/usr.bin/xlint/lint2/msg_???.ln.
This change means that usr.bin/error no longer recognizes these messages as coming from lint2, but that can be fixed later if necessary.
|
1.4 | 30-Aug-2021 |
rillig | branches: 1.4.4; tests/lint: test writing and reading .ln files
The test case for reading varargs functions is no longer necessary, the code is covered by the newly added tests as well.
Test inline function and return value usage.
|
1.3 | 30-Aug-2021 |
rillig | tests/lint: test reading of varargs, printflike, scanflike
|
1.2 | 30-Aug-2021 |
rillig | lint: revert "remove redundant call to strchr" from yesterday
This "refactoring" broke the parsing code for varargs, printflike and scanflike functions, and there were no tests for these. Revert for now, maybe try again later, after adding the corresponding tests.
|
1.1 | 07-Aug-2021 |
rillig | tests/lint: add test for reading the lint1 output
|
1.4.4.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.9 | 05-Nov-2024 |
rillig | lint: fix cross references in comments
|
1.8 | 02-Aug-2023 |
rillig | branches: 1.8.2; lint: distinguish between arguments and parameters
|
1.7 | 03-Jul-2023 |
rillig | lint: rename uppercase QUAD to LLONG
No binary change.
|
1.6 | 22-May-2023 |
rillig | lint: rename constant NOTSPEC to NO_TSPEC
It was too easy to misread the old name as NOT_SPEC instead of the intended NO_TSPEC.
|
1.5 | 30-Aug-2021 |
rillig | tests/lint: test writing and reading .ln files
The test case for reading varargs functions is no longer necessary, the code is covered by the newly added tests as well.
Test inline function and return value usage.
|
1.4 | 30-Aug-2021 |
rillig | tests/lint: test reading of varargs, printflike, scanflike
|
1.3 | 30-Aug-2021 |
rillig | lint: revert "remove redundant call to strchr" from yesterday
This "refactoring" broke the parsing code for varargs, printflike and scanflike functions, and there were no tests for these. Revert for now, maybe try again later, after adding the corresponding tests.
|
1.2 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.1 | 07-Aug-2021 |
rillig | tests/lint: add test for reading the lint1 output
|
1.8.2.1 | 02-Aug-2025 |
perseant | Sync with HEAD
|
1.1 | 07-Aug-2021 |
rillig | tests/lint: test reading of 128-bit integer types and printf
|
1.2 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.1 | 07-Aug-2021 |
rillig | tests/lint: test reading of 128-bit integer types and printf
|
1.1 | 07-Aug-2021 |
rillig | tests/lint: test reading of 128-bit integer types and printf
|
1.3 | 24-Aug-2021 |
rillig | tests/lint: normalize whitespace in lint2 tests
Found a typo in read.ln, f124, which had just 'F' instead of the intended 'F0'. Other than that, only whitespace changes.
|
1.2 | 08-Aug-2021 |
rillig | tests/lint: test passing of printf-like strings between lint1 and lint2
|
1.1 | 07-Aug-2021 |
rillig | tests/lint: test reading of 128-bit integer types and printf
|
1.13 | 16-Dec-2021 |
rillig | tests/lint: fix copy-and-paste typo in comment
|
1.12 | 16-Dec-2021 |
rillig | lint: improve error message for missing newline in .ln file
|
1.11 | 16-Dec-2021 |
rillig | tests/lint: demonstrate bad error message on missing newline
|
1.10 | 28-Nov-2021 |
rillig | lint2: in case of parse errors, output the offending line
This provides more of a clue than a simple '(not alnum or _: )', especially in the output of build.sh.
While here, change the format of the error message to the standard '%s:%d'. Since these are internal errors, they are not supposed to occur often, so no need to change error(1).
|
1.9 | 28-Nov-2021 |
rillig | tests/lint2: fix regular expressions containing backslash
In regular expressions, a backslash must be doubled. In this case, ATF didn't complain because the single backslashes were used in the pattern '\($2\)', where they produced '\(...\\)'. Omitting the backslash for the closing parenthesis was apparently OK; other regex implementations complain about this.
|
1.8 | 05-Sep-2021 |
rillig | lint: hide irrelevant type information from lint2
No functional change.
|
1.7 | 04-Sep-2021 |
rillig | tests/lint: test error handling when reading .ln files
|
1.6 | 24-Aug-2021 |
rillig | lint: allow libraries to use 128-bit integer types
|
1.5 | 08-Aug-2021 |
rillig | tests/lint: include but don't run read_lp64 on 32-bit platforms
The lint1 tests are all in the machine-independent file list, which makes it easier to manage them. At run time, some of them are skipped based on platform characteristics. Do the same for the lint2 tests.
Having the lint2 test named read_lp64 as the only machine-dependent test would complicate things.
The build for i386 had failed because the files for read_lp64 were listed in distrib/sets/lists/tests/mi but were not actually installed.
|
1.4 | 08-Aug-2021 |
rillig | tests/lint: make list of tests simpler
Since the file /usr/tests/usr.bin/xlint/lint2/tests has only been in the file set for a few minutes, it is not marked as obsolete but simply removed.
|
1.3 | 07-Aug-2021 |
rillig | tests/lint: test reading of 128-bit integer types and printf
|
1.2 | 07-Aug-2021 |
rillig | tests/lint: add test for reading the lint1 output
|
1.1 | 05-Aug-2021 |
rillig | tests/lint: add test skeletons for messages from lint2
|