This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Antwort: Re: [plugins] [patch] Initial implementation of GCC plugin support


Diego Novillo 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.

I agree.

The critical thing is that the FSF releases reject plugins that do not
match the compiler exactly -- unless the user explicitly requests
otherwise.  Distributors may of course make different decisions, but we
must err on the side of robustness.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]