On Monday, March 21, 2016 at 5:15:30 PM UTC-4, Gaetano Mendola wrote: > > On Monday, 21 March 2016 01:37:00 UTC+1, Jeffrey Walton wrote: >> >> Mixing and matching compilers is a bad idea. Also see >> https://cryptopp.com/wiki/Config.h#5.6.3_Recommendations . >> > > I do not agree with this, as far they use the same ABI interface I don see > any issue with that, I have used executable generated with clang linking > libraries generate with gcc. What I did miss out is that gcc started to abi > tag symbols and clang is not still able to understand it. >
Yeah, what we have found its more than simply an ABI compatibility. For example, the way exceptions crosses the app/library boundary matters, too. And as far as I know, the C++ committee does not dictate things like that so there are lots of one-off problems. Clang is a constant source of problems. It pretends to be GCC on Linux and MSVC on Windows, but it cannot consume the same set of programs as the compiler its pretending to be. It also does provide the same behaviors in a program as the compilers its pretends to be. The problem is compounded because Apple Clang and LLVM Clang has different versioning schemes and slightly different personalities. If you have not experienced problems, then you've probably been getting lucky (up until now). Advanced folks like you can probably work around them. Many users cannot. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
