This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients benjamin.peterson, pitrou, siddhesh, steve.dower, vstinner
Date 2018-10-23.10:22:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540290121.37.0.788709270274.issue33015@psf.upfronthosting.co.za>
In-reply-to
Content
> gcc8.1 throws this warning irrespective of the cast since converting function pointers may result in undefined behaviour unless it is cast back to its original type.

Do you have a reference explaining this issue? I dislike adding a memory allocation to call a function just to fix a compiler warning. From my point of view, at the end, the function pointer is just an integer. I don't understand how an additional memory allocation solves the issue.
History
Date User Action Args
2018-10-23 10:22:01vstinnersetrecipients: + vstinner, pitrou, benjamin.peterson, steve.dower, siddhesh
2018-10-23 10:22:01vstinnersetmessageid: <1540290121.37.0.788709270274.issue33015@psf.upfronthosting.co.za>
2018-10-23 10:22:01vstinnerlinkissue33015 messages
2018-10-23 10:22:01vstinnercreate