This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: Support non-standard extension (call via casted function pointer)
- From: Michael Karcher <debian at mkarcher dot dialup dot fu-berlin dot de>
- To: Richard Biener <richard dot guenther at gmail dot com>, John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin dot de>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Debian m68k <debian-68k at lists dot debian dot org>, Andreas Schwab <schwab at linux-m68k dot org>, Matthias Klose <doko at debian dot org>
- Date: Tue, 26 Jan 2016 21:54:25 +0100
- Subject: Re: RFC: Support non-standard extension (call via casted function pointer)
- Authentication-results: sourceware.org; auth=none
- References: <56A697DE dot 5090207 at mkarcher dot dialup dot fu-berlin dot de> <85BF0BF8-F3BB-49F9-AA9F-5793017C7062 at gmail dot com> <56A73A99 dot 7030305 at physik dot fu-berlin dot de> <CAFiYyc0f7OzQqZQ72k9SwiPsmOBxTYPE2v88XahcJGJ_Y0zCGg at mail dot gmail dot com> <56A7C307 dot 3010701 at mkarcher dot dialup dot fu-berlin dot de> <9B390CB8-DA78-4811-8191-471BEC84DA1C at gmail dot com>
On 26.01.2016 21:47, Richard Biener wrote:
>>> So, hookize and change to
>>>
>>> if (outgoing && POINTER_TYPE_P (TREE_TYPE (TREE_TYPE (func))))
>>> ...
>>> else if (POINTER_TYPE_P (valtype))
>>> ...
>>> else
>>> ...
>> Looks good and clean to me, but I expect my patch to have the same
>> effect.
> I would still prefer the more obvious approach of using the target hook transition.
I intended to express in my last email: Me too, and I will prepare a
patch with a target hook if there is consensus that this patch can be
accepted. I do not want the current patch committed as-is, I just posted
it to get the idea across and start discussion.
Regards,
Michael Karcher