--- Comment #3 from bkoz at gcc dot gnu dot org 2009-01-24 02:45 ---
Please note there are no ABI baseline files checked in to the FSF GCC
repository for darwin for this (or any) release on this (or any) architecture.
Without these, there can be no automated ABI testing by the GCC community.
Thus, there is no ABI to break for your release/target, and this bug is
invalid.
If this is something you'd like to see supported on your target in the future,
please consider activating the make check-abi rule and checking in the ABI
baseline files (baseline_symbols.txt) to the
config/abi/post/[powerpc|i686]_darwin directories.
Now, to answer the stated question.
On x86_64-linux-gnu, gcc-4.0.4 has the following stdio_filebuf exports in
baseline_symbols.txt:
OBJECT:24:_ZTIN9__gnu_cxx13stdio_filebufIcSt11char_traitsIcEEE@@GLIBCXX_3.4
OBJECT:24:_ZTIN9__gnu_cxx13stdio_filebufIwSt11char_traitsIwEEE@@GLIBCXX_3.4
OBJECT:49:_ZTSN9__gnu_cxx13stdio_filebufIcSt11char_traitsIcEEE@@GLIBCXX_3.4
OBJECT:49:_ZTSN9__gnu_cxx13stdio_filebufIwSt11char_traitsIwEEE@@GLIBCXX_3.4
These match gcc-4.2.4. Analysis of prior baseline_symbols.txt files (from
gcc-3.4.6) show similar exports for this class.
For the record, later versions of gcc, starting with gcc-4.3.0, still have only
these exports.
If darwin exported additional member functions in gcc-4.0.0 for stdio_filebuf,
then it did so in divergence with the linux baselines.
Hope this helps.
--
bkoz at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution||INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36173