This is the mail archive of the
mailing list for the GCC project.
Re: Fix class type lookup from OBJ_TYPE_REF
- From: Richard Biener <rguenther at suse dot de>
- To: Jan Hubicka <hubicka at ucw dot cz>, Mike Stump <mikestump at comcast dot net>
- Cc: David Edelsohn <dje dot gcc at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Jason Merrill <jason at redhat dot com>, martin jambor <mjambor at suse dot cz>, stanshebs at earthlink dot net
- Date: Mon, 19 Aug 2013 11:55:15 +0200
- Subject: Re: Fix class type lookup from OBJ_TYPE_REF
- References: <CAGWvnymPF5w9eqh2hctOK0hTw-0maWi76PAzVUQHPU-EzU-zEg at mail dot gmail dot com> <20130817155403 dot GD20005 at kam dot mff dot cuni dot cz> <B62A8D4D-93F6-4EA8-A743-221F31D892C8 at comcast dot net> <20130819090401 dot GB4758 at kam dot mff dot cuni dot cz>
Jan Hubicka <firstname.lastname@example.org> wrote:
>> On Aug 17, 2013, at 8:54 AM, Jan Hubicka <email@example.com> wrote:
>> > Moreover objc apparently never produce any virtual
>> Objective-C++ might. :-)
>Sure, those ought to be regular C++ methods though.
>> > Can someone explain me in greater detail how the objc use works?
>> Objective-C uses it to manage code generation for post-increments of
>method calls that involve a castâ in greater detail, no, that's just
>from a quick read of the code.
>OK, the real question is what objective-C expects middle end to do with
>If it expects it to do some optimization, it is probably wrong, since I
>am not aware
>of any OBJ_TYPE_REF code that will work on types w/o virtual tables.
>If it expects to do nothing, I guess we ought to drop it at
The handling is probably dependent no the runtime in use, so I suggest looking into Darwin specific files for example.