This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Antwort: Re: [plugins] [patch] Initial implementation of GCC plugin support
- From: Diego Novillo <dnovillo at google dot com>
- To: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- Cc: Taras Glek <tglek at mozilla dot com>, Markus Milleder <markus dot milleder at generali dot at>, benjamin at smedbergs dot us, Cupertino Miranda <cupertinomiranda at gmail dot com>, gcc-patches at gcc dot gnu dot org, Grigori Fursin <grigori dot fursin at inria dot fr>, "Joseph S. Myers" <joseph at codesourcery dot com>, Le-Chun Wu <lcwu at google dot com>, Sean Callanan <spyffe at cs dot sunysb dot edu>, Zbigniew Chamski <zbigniew dot chamski at gmail dot com>
- Date: Tue, 24 Feb 2009 13:51:06 -0500
- Subject: Re: Antwort: Re: [plugins] [patch] Initial implementation of GCC plugin support
- References: <OFC8650E0E.3CD3D4FA-ONC1257567.003E9999-C1257567.00404D25@AT.TOP.COM> <49A43870.60906@mozilla.com> <49A43FC5.1020207@starynkevitch.net>
On Tue, Feb 24, 2009 at 13:43, Basile STARYNKEVITCH
<basile@starynkevitch.net> wrote:
> So perhaps adding an explicit -fdisable-plugin-version-check flag which
> would turn the error message into a warning or a notice could make sense. I
> am not sure if the plugin should decide to accept slightly incompatible
> versions (ie if we should differentiate, it should not be the plugin author
> to decide...) This is really a user decision.
Yes. This is reasonable. By default, GCC would do strict version
checking. If the user knows that the version check is not necessary,
a flag could disable the check. Of course, if the plugin runs into a
bug because of this, the user gets to keep both halves of the
compiler.
> And even the concern about bugs in plugins should not be a major one. I
> would find acceptable that during the first year of plugins, a policy as
> strong as "if there is a bug when using a plugin, we don't care and only the
> plugin author should care" would be mandatory.
This should be our long-term policy. I see three types of bugs here:
- Bugs introduced by a plugin. Easy to ignore.
- Bugs uncovered by a plugin. Depending what stage of development we
are in we may want to address/ignore it.
- Bugs uncovered by a plugin but reproducible without the plugin. We
address it as a regular bug.
Diego.