-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use -Werror and -Wpedantic in CI #238
base: workflow
Are you sure you want to change the base?
Conversation
This seems to be an issue with C more than anything else. The issue is discussed in N 1923 in detail, including workarounds, and a fix has been accepted in C23 as N 2607. The workarounds don't sound ideal, so perhaps we explicitly ignore this warning? |
Agree. It's an ISO C issue. :) We can ignore it. |
Unfortunately there does not appear to be any easy way to do this. There are no command line flags for GCC to selectively disable some ISO compliance checks, either it tests if the code is ISO C compliant or not. The only workaround would be to use pragmas to selectively disable |
If this costs too much time, it may not be worth it. Focus on fuzz may help us more. But if you want, we can change FFmpeg/libavcodec/vvc/vvc_intra_template.c Line 241 in e81b6d7
Thank you |
This patchset does two things:
-Werror
flag for only the libavcodec/vvc/*.o objects. This turns any compilation warnings for these files into CI failures.-Wpedantic
flag, which adds warnings whenever non-standard C features are used. This should help catch errors such as that fixed by FFmpeg/FFmpeg@75e3b81Note these stricter compilation settings fail with the current HEAD, due to the error:
in this location and various others.