aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/exr.c
diff options
context:
space:
mode:
authorAndreas Rheinhardt <andreas.rheinhardt@outlook.com>2024-02-23 18:54:10 +0100
committerAndreas Rheinhardt <andreas.rheinhardt@outlook.com>2024-02-26 22:09:19 +0100
commit25e0e087c4314730d42ac16061962904b8fb3ae6 (patch)
tree109c6a2d285d2a5160ec42545b8db8f95ac9dd34 /libavcodec/exr.c
parent84e669167de9394e0de1bee0244f48ffac6f3826 (diff)
downloadffmpeg-25e0e087c4314730d42ac16061962904b8fb3ae6.tar.gz
configure: Disable linker warnings for common symbols
Common symbols are not part of ISO-C and therefore not used by FFmpeg at all. Yet linker warnings to ensure it stays that way are nevertheless wrong, because the existence of common symbols does not imply that there is a bug in our code. More precisely, Clang's ASAN implementation uses a common symbol ___asan_globals_registered when used on Elf targets with the -fsanitize-address-globals-dead-stripping option; said option is the default since Clang 17 [1]. This leads to 1883 warnings about ___asan_globals_registered when linking here. (Even without that option there were warnings like _ZN14__interception10real_vforkE being overridden.) Said warning is also unnecessary: The proper way to ensure that our code is free of common symbols is to let the compiler enforce this. But this is already the default since GCC 10 and Clang 11, so there is no risk of introducing our own common symbols. [1]: https://reviews.llvm.org/D152604 Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Diffstat (limited to 'libavcodec/exr.c')
0 files changed, 0 insertions, 0 deletions