Jeff Law writes:
>> If you build sth as part of GCC then why is it a plugin in the first place?
> I think we want plugins for domain-specific analysis. Having a
> repository for well developed checkers makes sense to me, particularly
> for checkers which are useful across projects.
>
> One such
On 03/14/2017 07:44 AM, Richard Biener wrote:
On Tue, Mar 14, 2017 at 2:38 PM, Nick Clifton wrote:
Hi Richard,
I was thinking that it would be nice to make plugins a "first-class
citizen" in the gcc world by having a proper directory structure and
integration into the rest of gcc.
I bel
On Tue, Mar 14, 2017 at 2:38 PM, Nick Clifton wrote:
> Hi Richard,
>
>>> I was thinking that it would be nice to make plugins a "first-class
>>> citizen" in the gcc world by having a proper directory structure and
>>> integration into the rest of gcc.
>
>> I believe plugins are currently a hack
Hi Richard,
>> I was thinking that it would be nice to make plugins a "first-class
>> citizen" in the gcc world by having a proper directory structure and
>> integration into the rest of gcc.
> I believe plugins are currently a hack due to the lack of a clearly defined
> API to access GCC inte
On Mon, Mar 13, 2017 at 6:12 PM, Nick Clifton wrote:
> Hi Guys,
>
> I was thinking that it would be nice to make plugins a "first-class
> citizen" in the gcc world by having a proper directory structure and
> integration into the rest of gcc. For example:
>
> gcc/plugins <--
Hi Guys,
I was thinking that it would be nice to make plugins a "first-class
citizen" in the gcc world by having a proper directory structure and
integration into the rest of gcc. For example:
gcc/plugins <-- Everything plugin-y starts here
gcc/plugins/Make-lang.in <--
