This is the mail archive of the gcc@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: [plugin] Directory for plugins distributed with gcc

From: Rafael Espindola <espindola at google dot com>
To: Diego Novillo <dnovillo at google dot com>
Cc: Olatunji Ruwase <tjruwase at google dot com>, gcc at gcc dot gnu dot org
Date: Thu, 16 Jul 2009 14:08:52 +0100
Subject: Re: [plugin] Directory for plugins distributed with gcc
References: <fe7fd8170907151130j35ac3348kb447e7e1d273d9af@mail.gmail.com> <b798aad50907151143v5abe42daj897861ed5591724c@mail.gmail.com> <fe7fd8170907151150g134348c1k5c2ef1a053c57cd2@mail.gmail.com> <b798aad50907151214w5c8fceeyf4dd838edd2e1cfc@mail.gmail.com>

> In general I think spinning off modules/passes that are not used very
> frequently (e.g. the tree browser) is a good idea since it reduces the
> size of our code base.

I would go a  bit further.

One nice properties of plugins is that they have a more restrictive
API. That should help us to get the code a bit more maintainable.

Olatunji's work is a very nice example. For example, to make mudflap a
plugin he had to remove the occurrences of  "if (flag_mudflap)" and
make mudflap use the existing generic varpool.

>
> Diego.
>


Cheers,
-- 
Rafael Avila de Espindola

Google | Gordon House | Barrow Street | Dublin 4 | Ireland
Registered in Dublin, Ireland | Registration Number: 368047

References:
- Re: [plugin] Directory for plugins distributed with gcc
  - From: Diego Novillo
- Re: [plugin] Directory for plugins distributed with gcc
  - From: Olatunji Ruwase
- Re: [plugin] Directory for plugins distributed with gcc
  - From: Diego Novillo

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