Per the comment at the end of bug #1075: > ------- Additional Comments From jturner > 06/29/99 13:46 ------- > Are you still seeing this bug with egcs-1.1.2-12 > (distributed with 6.0)? Reopen this bug if you are > still seeing these problems. ... the test program included in the bug reports still generates incorrect output on a RH 6.0 system: $ uname -a Linux ba2.cs.rpi.edu 2.2.10 #8 SMP Fri Jun 25 20:01:48 EDT 1999 i686 unknown $ g++ -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
If I understand the discussion of bug #1075 correctly, the problem cannot be solved without changing the C++ ABI (one way or the other, either to -fno-vtable-thunks, or for the "ABI overhaul" which Jason referred to on egcs-bugs). The current plan (and subject to all the usual disclaimers about we don't preannounce releases or however those disclaimers go) is that we are not going to change the C++ ABI in the next release of Red Hat Linux (for example, we will ship egcs 1.1.2 rather than gcc 2.95).