-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Diego Novillo wrote:
> Before plug-ins: put your gimple-to-myIR converter in passes.c > After plug-ins: dlopen gimple-to-myIR.so > > Both represent the same effort. Both require your converter to be kept > up-to-date with GCC's ever shifting ABI/API. They represent the same effort for somebody writing a plugin pass. They do *not* represent the same effort for a Mozilla hacker who just wants to compile Mozilla with the extra static-checking pass enabled. The fact that they can use a stock GCC (and potentially a precompiled plugin specific to their GCC version) is a huge advantage. Note that we're talking about analysis passes that would never be appropriate for integration with GCC directly: e.g. "statically enforce that the internal typedef PRBool is only ever 0 or 1" or "statically enforce that pointers to subclasses of MMgc::GCObject allocated on the heap are only written through this particular writebarrier pattern"... so arguments about whether we want the code to be integrated into GCC itself are irrelevant. - --BDS - -- Benjamin Smedberg Platform Guru Mozilla Corporation [EMAIL PROTECTED] http://benjamin.smedbergs.us/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPdQkSSwGp5sTYNkRAjbiAKCPnFBPN4wXswT35dSx3gpyZv+DWACg3L8X 0ntugTV0nMoJoMTXa1yX+FE= =V32a -----END PGP SIGNATURE-----