There was an error in the abi for g++3.2x . By default the fixed
abi isn't used in g++3.3 to ensure the advertised abi compatibility
across g++ 2.2 and 2.3, but the fixed abi can be selected with
-fabi-version=0 . This fixes some issues with ublas in boost.
Since gcc 3.3 is being used exclusively in redhat severn, could this
compiler flag be used by default to ensure a (more) correct ABI
is used for C++?
On Thu, Jul 31, 2003 at 05:10:45AM -0400, Jakub Jelinek (???) wrote:
But gcc 3.2.x is compatible with gcc 3.3.x (there are some corner
but I believe gcc 3.2.x would simply ICE on them rather than generating
ABI incompatible code with gcc 3.3.x).