This is the mail archive of the
mailing list for the GCC project.
Re: [I don't think it's off-topic at all] Linking speed for C++
- To: Joe Buck <jbuck at synopsys dot COM>
- Subject: Re: [I don't think it's off-topic at all] Linking speed for C++
- From: Richard Henderson <rth at redhat dot com>
- Date: Thu, 10 May 2001 16:22:59 -0700
- Cc: Andreas Jaeger <aj at suse dot de>, biswapesh dot chattopadhyay at bt dot com, gcc at gcc dot gnu dot org, bastian at suse dot com
- References: <20010510101446.A27465@redhat.com> <200105101816.LAA22843@toledo.synopsys.com>
On Thu, May 10, 2001 at 11:16:39AM -0700, Joe Buck wrote:
> The vtable_pic attribute may be applied to a base class (that is, a class
> that is not derived from another class). If present, the vtable is
> generated in offset form (function address minus vtable address);
> The vtable_stubs attribute may be applied to a derived class,
> provided that some base class has the vtable_pic attribute. This
> attribute is intended for use when the definitions of the member
> functions of the derived class are in a different dso than the
> functions of the base class.
I suspect that this will be hard for people to use in practice.
> Exception handling is also non-PIC; sorry, I don't know enough about
> the current implementation to have any suggestions for reducing the
> number of relocations.
This is being addressed in the new eh implementation.