This is the mail archive of the
mailing list for the GCC project.
Re: RFC: Support non-standard extension (call via casted function pointer)
- From: Jeff Law <law at redhat dot com>
- To: John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin dot de>, Richard Biener <richard dot guenther at gmail dot com>, Michael Karcher <debian at mkarcher dot dialup dot fu-berlin dot de>, gcc at gcc dot gnu dot org
- Cc: Debian m68k <debian-68k at lists dot debian dot org>, Andreas Schwab <schwab at linux-m68k dot org>, doko at debian dot org
- Date: Tue, 26 Jan 2016 08:50:57 -0700
- 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>
On 01/26/2016 02:21 AM, John Paul Adrian Glaubitz wrote:
Not as-is. But they make a starting point for trying to address the
problem -- particularly the testcases, even if they are ill-formed to a
On 01/26/2016 08:01 AM, Richard Biener wrote:
I developed a gcc patch that does not change the code generation for
conforming programs but fixes this non-conforming use-case by always
taking the actual return type in the call expression into account, even
if the function declaration to be called is known. Please comment
whether such a patch has any chance to be applied to either gcc
or gcc in Debian.
Without looking at the patch this is already how GCC should behave for all targets.
So, would you actually favor the inclusion of Michael's changes?
Having gcc allow to work with such code would actually allow us
to bootstrap ghc on m68k again which would be awesome :).