From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: Richard Guenther <richard.guenther@gmail.com>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: "plugin"-ifying the MELT branch.
Date: Tue, 16 Jun 2009 11:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0906161135370.2982@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4A378033.3080504@starynkevitch.net>
On Tue, 16 Jun 2009, Basile STARYNKEVITCH wrote:
> I thought on the contrary that is was expected that some code would become FSF
> owned plugins?
Not without a mechanism for linking plugins in statically on hosts for
which we don't support dynamic loading of plugins, and even then it's
doubtful. Rather, we should watch out for things being implemented as
plugins that are generally useful for GCC and seek to build them into GCC
(unconditionally) where appropriate, while leaving cases such as checking
project-specific coding rules as separate plugins.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-06-16 11:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 18:33 Basile STARYNKEVITCH
2009-06-05 16:14 ` Tom Tromey
2009-06-16 11:13 ` Basile STARYNKEVITCH
2009-06-16 11:16 ` Richard Guenther
2009-06-16 11:21 ` Basile STARYNKEVITCH
2009-06-16 11:38 ` Joseph S. Myers [this message]
2009-06-16 12:22 ` Basile STARYNKEVITCH
2009-06-16 12:53 ` Richard Guenther
2009-06-16 13:10 ` Joseph S. Myers
2009-06-16 17:10 ` Janis Johnson
2009-06-16 17:20 ` Diego Novillo
2009-06-16 17:30 ` Basile STARYNKEVITCH
2009-06-17 10:49 ` Richard Guenther
2009-06-17 11:56 ` Basile STARYNKEVITCH
2009-06-16 17:33 ` Joseph S. Myers
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=Pine.LNX.4.64.0906161135370.2982@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.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).