-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
gcc: fix some compiler errors from the new GCC #1658
Conversation
I think we may want to cancel those outdated CI jobs for this PR manually to make room for the latest one. @azat |
New failure arose, caused by Bug 106416 - -Wint-conversion should be an error, not a pedwarn |
0b674f0
to
79d764e
Compare
Still something wrong |
Yes, with -Wincompatible-pointer-types and -Wint-conversion being turned into error level on MinGW somehow, lots of code in |
It should be pretty easy to fix, there is another option - turn off those warning for mingw build, but I don't like this idea |
Finally, all new compiler errors are fixed! https://github.com/libevent/libevent/actions/runs/9168188585/job/25206570042?pr=1658 I think we're good to go. |
Ping @azat |
--------- Signed-off-by: Andy Pan <i@andypan.me>
--------- Signed-off-by: Andy Pan <i@andypan.me>
--------- Signed-off-by: Andy Pan <i@andypan.me>
--------- Signed-off-by: Andy Pan <i@andypan.me>
Thank you! Now LGTM (will merge once mingw build will pass) |
New compiler errors to be fixed:
[-Wincompatible-pointer-types]
,[-Wint-conversion]
, and[-Wcast-function-type]
The CI failure for -Wincompatible-pointer-types may have something to do with this GCC patch. See also this llvm/llvm-project#74605.
Thus, I think we should explicitly cast the
int
pointer to the expected type to avoid these compiler errors.@azat