This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Plugins & GGC ie GTY
- From: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- To: Richard Guenther <richard dot guenther at gmail dot com>
- Cc: Taras Glek <tglek at mozilla dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>, Diego Novillo <dnovillo at google dot com>, Le-Chun Wu <lcwu at google dot com>, Grigori Fursin <grigori dot fursin at inria dot fr>
- Date: Wed, 01 Apr 2009 20:37:21 +0200
- Subject: Re: Plugins & GGC ie GTY
- References: <49D25E40.6080507@mozilla.com> <84fc9c000904010146j53e49ed9i6c271751d41dfd42@mail.gmail.com> <Pine.LNX.4.64.0904011257550.14922@digraph.polyomino.org.uk> <49D398C9.1010809@mozilla.com> <49D3A2CA.7030603@starynkevitch.net> <84fc9c000904011126o75a10641oc4bcbe810cdb2d29@mail.gmail.com>
Richard Guenther wrote:
Plugins shouldn't keep permanent references to GCed memory. At least
that would make it unnecessary to do what you suggest.
I strongly disagree with that, and I simply do not understand your
position. In my perception, plugins are essentially loaded (dlopen-ed)
but never unloaded (dlclose-ed; perhaps they would be dlclose-ed when
every thing is done). Why should they not use any GTY stuff? What makes
you think that some features of GCC (like GTY ...) are invalid inside
plugins?
I find your position as extreme as saying: plugins should never call
malloc or xcalloc, or should never call warning_at, or should never call
XXX! Why?
So what are plugins for?
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***