Re: Compiler ABI changes and XPCOM components

Doug Turner <[email protected]> writes:
> 
> In any case, I think that my first posting was the most correct... "If 
> and when Mozilla upgrades the compiler they use, your component will 
> have to be rebuilt against the same compiler."  The word 'will' in the 
> above statement could should have been 'may'.  There is a possiblity 
> that the ABI changes's are that bad.  But it could be the case that all 
> bets are off.
> 

Even if all components survive an ABI change, both Mozilla and some of
the plugins link directly against libstdc++.  So right now, I've got a
gcc 3.1 build on my disk which can't use the flash plugin, because
Mozilla is linked against the gcc 3.1 version of libstdc++, and the
plugin is expecting the name mangling of the old version.

That said, I think we should take a list of plugin developers and try
to get rough consensus that we should bite the bullet and upgrade
compilers, in large part because of the optimization wins we get can.

Dan