From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Taras Glek <tglek@mozilla.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Richard Guenther <richard.guenther@gmail.com>,
GCC Mailing List <gcc@gcc.gnu.org>,
Diego Novillo <dnovillo@google.com>,
Le-Chun Wu <lcwu@google.com>,
Grigori Fursin <grigori.fursin@inria.fr>
Subject: Plugins & GGC ie GTY
Date: Wed, 01 Apr 2009 17:22:00 -0000 [thread overview]
Message-ID: <49D3A2CA.7030603@starynkevitch.net> (raw)
In-Reply-To: <49D398C9.1010809@mozilla.com>
Hello All,
[I don't know if this discussion belongs to gcc@ or gcc-patches@ so I'm
sending it on gcc@ since I don't propose or discuss any code yet]
My understanding was that most plugins people are aware that somehow
some plugins would need to have static GTY-ed roots for the GGC machinery.
So it seems to me that we'll need :
1. The ability to run gengtype in a special mode for plugins, on the
source code of the plugin. to generate the gt-*.h files included by the
source code of the plugin. This would require a patch to gengtype.
2. The ability to handle, very probably using dlsym, or perhaps by
having a gcc_plugin_register_gty_table function called from the plugin
initialization routine, to plug the generated root tables (an array of
struct ggc_root_tab, which is defined in the generated gt-*.h files) of
the plugin into the GGC machinery. This would require a short patch to
ggc-common.c or similar ggc-*.c files.
Did I miss anything?
Regards.
PS. This is not an April Fool joke! I am quit serious about extra GTY-ed
roots. It is for me an essential & required condition to perhaps
transform the MELT branch into a mega-plugin.
--
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} ***
next parent reply other threads:[~2009-04-01 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49D25E40.6080507@mozilla.com>
[not found] ` <84fc9c000904010146j53e49ed9i6c271751d41dfd42@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0904011257550.14922@digraph.polyomino.org.uk>
[not found] ` <49D398C9.1010809@mozilla.com>
2009-04-01 17:22 ` Basile STARYNKEVITCH [this message]
2009-04-01 18:26 ` Richard Guenther
2009-04-01 18:37 ` Basile STARYNKEVITCH
2009-04-01 20:48 ` Basile STARYNKEVITCH
2009-04-01 22:49 Joern Rennecke
2009-04-01 23:40 ` Steven Bosscher
2009-04-02 5:34 ` Basile STARYNKEVITCH
2009-05-05 2:53 ` Justin Seyster
2009-05-05 6:09 ` Basile STARYNKEVITCH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D3A2CA.7030603@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=grigori.fursin@inria.fr \
--cc=joseph@codesourcery.com \
--cc=lcwu@google.com \
--cc=richard.guenther@gmail.com \
--cc=tglek@mozilla.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).