aboutsummaryrefslogtreecommitdiffstats
path: root/tests/base64.c
diff options
context:
space:
mode:
authorAndreas Rheinhardt <andreas.rheinhardt@outlook.com>2024-03-21 16:27:58 +0100
committerAndreas Rheinhardt <andreas.rheinhardt@outlook.com>2024-03-24 19:05:35 +0100
commit0d43adcbef9a061c95db60eb351937c27e2a0609 (patch)
tree11ddc6754305a3eb62e125686f8ef5c2600de21c /tests/base64.c
parentccd2b7f858d2b1d10a49629aa9b24055b7cc5646 (diff)
downloadffmpeg-0d43adcbef9a061c95db60eb351937c27e2a0609.tar.gz
configure: Explicitly check for static_assert, _Static_assert
C11 provides static assertions via _Static_assert and provides static_assert as a convenience define for this in assert.h. Our codebase uses the latter, as _Static_assert has actually already been deprecated in C23. Not all toolchains that declare support for C11 actually support it; e.g. MSVC 19.27 does not support _Static_assert, but somehow supports static_assert. MSVC 19.27 admits to be a "preview implementation of the ISO C11 standard", so this is not surprising (MSVC 19.28 does not come with this caveat). Furthermore some FATE boxes [1] use old GCC toolchains (with only experimental support for C11) where _Static_assert is supported, but assert.h does not provide the fallback define. They are broken since the first usage of static_assert. This commit therefore checks whether static_assert and _Static_assert work with assert.h included; if not, configure errors out. This intentionally drops support for MSVC 19.27. Users like the old FATE boxes above can still add -Dstatic_assert=_Static_assert to cflags as a workaround if desired. [1]: https://fate.ffmpeg.org/report.cgi?time=20240321123620&slot=sh4-debian-qemu-gcc-4.7 Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Diffstat (limited to 'tests/base64.c')
0 files changed, 0 insertions, 0 deletions