-fnew-abi and branching

[Jeffrey A Law]

  In message < Pine.LNX.4.10.9912290931120.18053-100000@fidel.cygnus.com >you wri
te:
  > > |   In private email, Jason suggested that doing the -fnew-abi
  > > | development (i.e., the parts that belong to the compiler, not the bits
  > > | we discussed regarding libio) need not be done on a branch.
  > 
  > I am also in favor of this.
Seems reasonable to me if it's easier for y'all.


  > > On libstdc++-v3, we recommend testing '-fnew-abi' and we're planning to
  > > make it the default.  Unless I'm mistaken, the new ABI experiment means
  > > "official libio" and "EGCS libio" would go out of sync.  Am I right?
  > > If so, I'd like we come up with a solution that makes it possible for
  > > us (on libstdc++-v3) to continue to test -fnew-abi on v-3 without
  > > breaking everything. 
  > 
  > v3, glibc, and egcs all have different versions of libio anyway. Perhaps
  > we could take this opportunity to synch them? I'd rather do the
  > experimental work on libio in v3, with Uli's approval and help, then muck
  > around in the egcs version. 
This definitely needs to be fixed and soon.  Based on previous experience
we do not want 3 divergent libio implementations.  In fact, I'm rather
disturbed to find that glibc & egcs have diverged -- that should not be
happening.

jeff