This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why does casting a function generate a run-time abort?
- From: Christoph Hellwig <hch at infradead dot org>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: Andrew Pinski <pinskia at physics dot uc dot edu>,Ziemowit Laski <zlaski at apple dot com>,Eric Botcazou <ebotcazou at libertysurf dot fr>,gcc List <gcc at gcc dot gnu dot org>
- Date: Fri, 18 Jun 2004 09:13:05 +0100
- Subject: Re: Why does casting a function generate a run-time abort?
- References: <200406180802.i5I82SV28765@tin.geop.uc.edu> <874qp9cmkg.fsf@taltos.codesourcery.com>
On Fri, Jun 18, 2004 at 01:11:43AM -0700, Zack Weinberg wrote:
> Andrew Pinski <pinskia@physics.uc.edu> writes:
>
> >> Lemme ask you why Objective-C message dispatch needs this. It's
> >> impossible to get "right" on IA64 and a few others.
> >
> > It is only needed with the NeXT^wApple runtime :) so ...
> > The GNU runtime does not produce these casts at all and is safe.
>
> Well, ok, but that doesn't answer my question.
It pretty much means, no Objective-C doesn't need it as the GNU runtime
shows it..