change wflags-orig.txt to wflags-lax.txt (details)
Solved the requested warning with exceptions. Also went through the exceptions tests and managed to remove about 2/3rds of them from the lax list that now either didn't have any warnings or warnings because of the test itself. (details)
Try to get full build completing by disabling a data-collection substep. (details)
Fix test-classification commands to detect more strict-capable tests. Remove such tests from the lax list. (details)
Add completion of work in progress mistakenly included in 584612d. Fix test string-api-coverage to be warning free. (details)
Changed some inline declarations to static or static inline (which are the same except for intent communication). This makes them more robust to inline changes. (details)
fix build problem by fixing unsupported C23 attribute in test (details)
Commit
faf9e1980e17d288281279a8ee128978108933dd
by Michael Brooks
Explicate the present state for test-suite programs being free of warnings.
Now, test-suite compilation occurs in either strict or lax "wflags" mode. Strict mode is equivalent to what used to be done for the `nowarn` folder, lax to the rest of the test suite. Makefile.am now owns a list of tests that opt for lax wflags. About 70% of the tests opt for lax.
Remove special handling for the `nowarn` folder. Now, it simply does not appear on the opt-for-lax list.
Remove former tests nowarn/fstream nowarn/list nowarn/string because, respectively io/io list/dlist-insert-remove collections/string-api-coverage obviate them by getting strict wflags.
Commit
e0330d2cd1a09857e7eda48e70140f0f25161679
by Michael Brooks
Remove unnecessary special case for zero_t in code gen that caused unused-variable warning in thunks.
Add instructions for tidying warnings (with the present zero_t case as its running example) as a "proposal."
The code gen change is safe because a corresponding case for one_t was always "missing" and the the variable at issue is never used meaningfully. (Prior work has size_t lowered as int. While that's a dubious choice, it's beyond what I'm fixing here.)
Mark these tests as now clean of warnings: array-collections/array-basic ctrl-flow/loopctrl vector vector_math/vec2_int vector_math/vec2_float vector_math/vec3_float vector_math/vec4_float zero_one
Commit
d3cf623098e72d98fd3ea76544061496946dbba4
by ajbeach
Solved the requested warning with exceptions. Also went through the exceptions tests and managed to remove about 2/3rds of them from the lax list that now either didn't have any warnings or warnings because of the test itself.
Commit
5251c6b3e179b007a0d6e799699a2ace9204dda2
by ajbeach
Changed some inline declarations to static or static inline (which are the same except for intent communication). This makes them more robust to inline changes.