Re: [Boost-testing] [XL C/C++][IBM_Canada_Ltd][serialization][multi_index]strange error with boost/serialization/force_include.hpp

Subject: Re: [Boost-testing] [XL C/C++][IBM_Canada_Ltd][serialization][multi_index]strange error with boost/serialization/force_include.hpp
From: Joaquin M Lopez Munoz (joaquin_at_[hidden])
Date: 2009-03-30 11:52:18

Robert Ramey <ramey <at> rrsd.com> writes:

> 
> joaquin <at> tid.es wrote:
> >
> > The problem lies in boost/serialization/force_include.hpp, which,
> > for reasons unbeknownst to me, defines BOOST_USED as the
> > compiler-specific qualifier __attribute__ ((used)). Looking at the
> > code for force_include.hpp (http://tinyurl.com/cpk7ux ) seems
> > like this definition of BOOST_USED can only take place if
> > either __GNUC__ or __INTEL_COMPILER is defined, which
> > does not seem to be the case here.
> 
> Last time I looked, this attribute was only supported on the compilers
> listed.  My understanding was that for the IBM compiler, this might
> change and perhaps it has.  Feel free to tweak force_include to
> see if that fixes the problem.

Thanks, I'll do that if nobody sheds more light on this, but my
puzzlement stems from the fact that BOOST_USED *shouldn't* be resolving
to __attribute__ ((used)) as far as I can see: XL C/C++ does *not*
define __GNUC__ or __INTEL_COMPILER (see http://tinyurl.com/66el78 ),
and I cannot see how else can BOOST_USED be defined as
__attribute__ ((used)).

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo