This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFA/RFC: Add support for exporting vtables based on dllexport/dllimportattributes
- From: Nick Clifton <nickc at redhat dot com>
- To: Michael Matz <matz at suse dot de>, s_fsfeurope2 at nedprod dot com
- Cc: mark at codesourcery dot com, jason at redhat dot com, gcc-patches at gcc dot gnu dot org, Andy dot Sizer at symbian dot com
- Date: Mon, 17 May 2004 09:58:35 +0100
- Subject: Re: RFA/RFC: Add support for exporting vtables based on dllexport/dllimportattributes
- References: <m3u0yjotkk.fsf@redhat.com> <Pine.LNX.4.58.0405170817550.29808@wotan.suse.de>
Hi Michael, Hi Niall,
This seems to do something similar to the patches for fixing PR9283
http://gcc.gnu.org/ml/gcc-patches/2004-05/msg00571.html
which are idlying since some time. Perhaps it could be incorporated into
that one?
It is in a similar arena, but it is not quite dealing with the same
issue. The visibility patch is more generic (affecting both C and C++)
and it is dealing with ELF attributes, whereas my patch is specific to a
couple of DLL models that are used by various OSes. Hence I do not
think that they are really suitable to be combined.
By the way Niall - have you signed an FSF copyright assignment so that
yours and Brian's patch can be accepted ? As far as I could tell from
the email archives this is the only thing that is holding up its
acceptance. If not then I am attaching an email form that you can use
to start the ball rolling. No transatlantic calls are involved, just
some email and probably a snail mail letter.
Cheers
Nick
---------------------------------------------------------------------------
request-assign.future:
Please email the following information to fsf-records@gnu.org, and we
will send you the assignment form for your past and future changes.
Please use your full name as the subject line of the message.
[What is the name of the program or package you're contributing to?]
[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]
[Do you have an employer who might have a basis to claim to own
your changes? Do you attend a school which might make such a claim?]
[For the copyright registration, what country are you a citizen of?]
[What year were you born?]
[Please write your email address here.]
[Please write your snail address here.]
[Which files have you changed so far, and which new files have you written
so far?]
---------------------------------------------------------------------------