From: Diego Novillo <dnovillo@google.com>
To: Olatunji Ruwase <tjruwase@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [plugin] Directory for plugins distributed with gcc
Date: Wed, 15 Jul 2009 19:14:00 -0000 [thread overview]
Message-ID: <b798aad50907151214w5c8fceeyf4dd838edd2e1cfc@mail.gmail.com> (raw)
In-Reply-To: <fe7fd8170907151150g134348c1k5c2ef1a053c57cd2@mail.gmail.com>
On Wed, Jul 15, 2009 at 14:50, Olatunji Ruwase<tjruwase@google.com> wrote:
> Sorry that I wasn't very specific with my question. I m currently
> wrapping up the conversion of
> mudflap into a plugin. Most of the required patches have being
> approved and committed, so I was
> thinking ahead as to where the the plugin code will reside.
Ah, this is a different issue. What you are proposing is to take
mudflap out of GCC and convert it into a separate plugin.
I don't really have a strong opinion on mudflap in particular. I
wouldn't mind making it a plugin, though. What do other folks think?
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.
Diego.
next prev parent reply other threads:[~2009-07-15 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fe7fd8170907151130j35ac3348kb447e7e1d273d9af@mail.gmail.com>
2009-07-15 18:43 ` Diego Novillo
2009-07-15 18:51 ` Olatunji Ruwase
2009-07-15 19:14 ` Diego Novillo [this message]
2009-07-15 19:36 ` Joseph S. Myers
2009-07-15 20:43 ` Paolo Bonzini
2009-07-15 20:53 ` Joseph S. Myers
2009-07-15 21:16 ` Basile STARYNKEVITCH
2009-07-15 21:43 ` Paolo Bonzini
2009-07-16 13:09 ` Rafael Espindola
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=b798aad50907151214w5c8fceeyf4dd838edd2e1cfc@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=tjruwase@google.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).