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
warning cleanup #2298
Comments
- timelocal() is nonstandard GNU extension, not recommended to be used and mktime() should be equivalent: * https://linux.die.net/man/3/timegm - GH #2298
- python2 is known for not confirming strict aliasing - it is EoL and likely not going to be fixed - GH #2298
I pushed patches for those warnings. The one of app_python is to disable the check, on the web people say python2 is known not to handle strict aliasing and being end-of-life, I guess is no chance to fix in the libs. For pdb: @henningw, @lbalaceanu & @smititelu - you are likely the devs familiar with the code, can you check the commit 86ebb4e and see if it is an acceptable solution? The idea was to get the |
- timelocal() is nonstandard GNU extension, not recommended to be used and mktime() should be equivalent: * https://linux.die.net/man/3/timegm - GH #2298 (cherry picked from commit a0fb220)
Closing, commits were also backported to 5.3. |
Hi i had to revert commit 86ebb4e because the return value wasn't correct anymore. It seems it just BR, |
@Earn330 - create a new bug report and reference this issue, so it does not get forgotten and we investigate it. |
ld_fld.c:273 implicit-function-declaration
redis_table.c:586 maybe-uninitialized
app_python strict-aliasing
pdb.c:348 address-of-packed-member]
The text was updated successfully, but these errors were encountered: