例如，我可以混合使用 GCC-4.6 和 GCC-4.9 编译的一组库吗？

我知道不同的编译器“品种”例如 VS 不能与 MinGW 一起使用，但不同代的同一编译器可以吗？有可能出现问题吗？如果有呢？

最佳答案

同一编译器的不同代有时可以相互兼容，但并非总是如此。例如，GCC 4.7.0 changed its C/C++ ABI ，这意味着使用 4.7.0+ 和 4.7.0- 编译的库不太可能相互兼容(因此在您的示例中，使用 4.6 编译的库将不与使用编译的库兼容4.9)。在给定的编译器版本中也可能存在 ABI 错误，as happened in GCC 4.7.0/4.7.1 :

GCC versions 4.7.0 and 4.7.1 had changes to the C++ standard library which affected the ABI in C++11 mode: a data member was added to std::list changing its size and altering the definitions of some member functions, and std::pair's move constructor was non-trivial which altered the calling convention for functions with std::pair arguments or return types. The ABI incompatibilities have been fixed for GCC version 4.7.2 but as a result C++11 code compiled with GCC 4.7.0 or 4.7.1 may be incompatible with C++11 code compiled with different GCC versions and with C++98/C++03 code compiled with any version.

The GCC ABI Policy and Guidelines page表示他们试图保持向前兼容性，但不保持向后兼容性:

Versioning gives subsequent releases of library binaries the ability to add new symbols and add functionality, all the while retaining compatibility with the previous releases in the series. Thus, program binaries linked with the initial release of a library binary will still run correctly if the library binary is replaced by carefully-managed subsequent library binaries. This is called forward compatibility.

The reverse (backwards compatibility) is not true. It is not possible to take program binaries linked with the latest version of a library binary in a release series (with additional symbols added), substitute in the initial release of the library binary, and remain link compatible.

该页面还对 GCC 用于标记给定组件的不同版本的版本控制系统进行了一些相当长的解释，以及对 GCC 本身背后的版本控制的解释:

Allowed Changes

• The following will cause the library minor version number to increase, say from "libstdc++.so.3.0.4" to "libstdc++.so.3.0.5".

• Adding an exported global or static data member

• Adding an exported function, static or non-virtual member function

• Adding an exported symbol or symbols by additional instantiations

• Other allowed changes are possible.

Prohibited Changes

The following non-exhaustive list will cause the library major version number to increase, say from "libstdc++.so.3.0.4" to "libstdc++.so.4.0.0".

• Changes in the gcc/g++ compiler ABI

• Changing size of an exported symbol

• Changing alignment of an exported symbol

• Changing the layout of an exported symbol

• Changing mangling on an exported symbol

• Deleting an exported symbol

• Changing the inheritance properties of a type by adding or removing base classes

• Changing the size, alignment, or layout of types specified in the C++ standard. These may not necessarily be instantiated or otherwise exported in the library binary, and include all the required locale facets, as well as things like std::basic_streambuf, et al.

• Adding an explicit copy constructor or destructor to a class that would otherwise have implicit versions. This will change the way the compiler deals with this class in by-value return statements or parameters: instead of passing instances of this class in registers, the compiler will be forced to use memory. See the section on Function Calling Conventions and APIs of the C++ ABI documentation for further details.

注意加粗的部分。在一个完美的世界中，具有相同主要版本号的 GCC 版本将是二进制兼容的。这不是一个完美的世界，所以在混合这样的编译器版本之前要非常仔细地测试，但总的来说你可能会没事的。

关于c++ - 你能混合使用同一个编译器的不同版本编译的c++吗，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/23895081/