https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703
Alan Modra changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703
--- Comment #7 from Alan Modra ---
Created attachment 34539
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34539&action=edit
prototype patch
How does this look as a potential fix? Obviously I'd need to provide the new
targetm field and ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703
--- Comment #6 from Alan Modra ---
Re comment #2, yes I agree that conversion between void* or pointer to object
and pointer to function is not strictly allowed. Fixing that by way of a union
was one of the first things I tried, before looking a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703
--- Comment #5 from Andreas Schwab ---
A conversion between an integer type and a pointer type is
implementation-defined, not undefined.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703
--- Comment #4 from Jakub Jelinek ---
(In reply to Richard Biener from comment #3)
> The tree level gets this right and on x86_64 RTL expansion looks ok as well.
> Can it be that PPC relies on REG_POINTER stuff and maybe the function
> pointer is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Target|
