Re: [v3] Provide Solaris 2 libstdc++ baseline files

[Paolo Carlini <paolo dot carlini at oracle dot com>]

Hi Rainer,

[skipping the detailed analysis, let me know if there is something we
should do because it affects non-Solaris systems]
> Ok for mainline after that testing has passed?
>   
Sure. Under the usual preconditions that the Changes you are proposing
have no effect for any other target, the approval is essentially obvious.
> And what about updating the baselines in the future if new symbols are
> added?  I suppose I can do that myself without explicit approval?
>   
I'm not sure to follow the reasoning here: as we mean it,  a baseline,
by definition, *never* changes, it's sort-of a concrete surrogate of an
ABI which we don't want to break. Then, given the baseline, we want to
check that successive minor versions of the library only add symbols,
versioned at the corresponding minor version, and never remove symbols
or add symbols at previous (older) minor versions. Indeed, this is what
abi_check does. Thus, I'm not sure to follow your reasoning... Granted,
something is special here about adding the baselines *now*, because
normally the baselines we have correspond to the gcc3.4.0 symbols, but
anyway, the general rule about the correct way of moving forward without
breaking old executables should stay the same, in particular no changes
to the baselines, etc.

Paolo.