https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90648
Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #7) > Some checking is needed even if the C FE is improved, in particular, one can > do stuff like: > return ((int (*) (int)) memcpy) (5); > etc. I agree the frontend should be improved (I've said so for years). I'll see how to make the genmatch machinery more robust here. Or rather get_call_combined_fn. Of course some builtins like __builtin_mul_overflow are hard to verify since they are variadic functions for the purpose of being type-generic. One can only hope the frontends do at least some sanity checking on them before declaring them builtins.. Similarly internal functions cannot have any sanity checking because they lack a prototype.