EGCS 1.1 Caveats

• EGCS has an integrated libstdc++, but does not have an integrated libg++. Furthermore old libg++ releases will not work with EGCS; HJ Lu has made a libg++-2.8.1.2 snapshot available which may work with EGCS.
  Note most C++ programs only need libstdc++.
• Exception handling may not work with shared libraries, particularly on alphas, hppas, rs6000/powerpc and mips based platforms. Exception handling is known to work on x86-linux platforms with shared libraries.
• Some versions of the Linux kernel have bugs which prevent them from being compiled or from running when compiled by EGCS. See the FAQ (as shipped with EGCS 1.1) for additional information.
• In general, EGCS is more rigorous about rejecting invalid C++ code or deprecated C++ constructs than g++-2.7, g++-2.8 or EGCS 1.0. As a result it may be necessary to fix C++ code before it will compile with EGCS.
• G++ is also converting toward the ISO C++ standard; as a result code which was previously valid (and thus accepted by other compilers and older versions of g++) may no longer be accepted.
• EGCS 1.1 compiled C++ code is not binary compatible with EGCS 1.0.x or GCC 2.8.x due to changes necessary to support thread safe exception handling.

Please send FSF & GNU inquiries & questions to gnu@gnu.org. There are also other ways to contact the FSF.

These pages are maintained by the GCC team.

For questions related to the use of GCC, please consult these web pages and the GCC manuals. If that fails, the gcc-help@gcc.gnu.org mailing list might help.
Please send comments on these web pages and the development of GCC to our developer mailing list at gcc@gnu.org or gcc@gcc.gnu.org. All of our lists have public archives.

Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110, USA.

Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

Last modified 2006-06-21