munit hits some new warnings in gcc-11: ``` CC tests/unit-tests/munit/munit.o ../tests/unit-tests/munit/munit.c:1836:47: warning: argument 4 of type ‘char * const[argc + 1]’ declared with mismatched bound ‘argc + 1’ [-Wvla-parameter] 1836 | int argc, char* const argv[MUNIT_ARRAY_PARAM(argc + 1)], | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from ../tests/unit-tests/munit/munit.c:118: ../tests/unit-tests/munit/munit.h:478:51: note: previously declared as ‘char * const[argc + 1]’ with bound ‘argc + 1’ 478 | int argc, char* const argv[MUNIT_ARRAY_PARAM(argc + 1)], | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../tests/unit-tests/munit/munit.c:2053:40: warning: argument 4 of type ‘char * const[argc + 1]’ declared with mismatched bound ‘argc + 1’ [-Wvla-parameter] 2053 | int argc, char* const argv[MUNIT_ARRAY_PARAM(argc + 1)]) { | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from ../tests/unit-tests/munit/munit.c:118: ../tests/unit-tests/munit/munit.h:463:86: note: previously declared as ‘char * const[argc + 1]’ with bound ‘argc + 1’ 463 | int munit_suite_main(const MunitSuite* suite, void* user_data, int argc, char* const argv[MUNIT_ARRAY_PARAM(argc + 1)]); | ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ``` I do not yet understand why `argc + 1` would be different from `argc +1` . Still happens even if I remove `MUNIT_ARRAY_PARAM` -- which of course it does because on my platform that macro does nothing.
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by roblatham00 and has received 3 comments.