Re: [Boost-bugs] [Boost C++ Libraries] #9766: boost >= 1.54 failes to compile with gcc-4.8.2 and LTO enabled

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #9766: boost >= 1.54 failes to compile with gcc-4.8.2 and LTO enabled
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-02-14 10:04:22

#9766: boost >= 1.54 failes to compile with gcc-4.8.2 and LTO enabled
-------------------------------+---------------------
  Reporter:  steffen@…         |      Owner:  andysem
      Type:  Bugs              |     Status:  closed
 Milestone:  To Be Determined  |  Component:  log
   Version:  Boost 1.54.0      |   Severity:  Problem
Resolution:  fixed             |   Keywords:
-------------------------------+---------------------

Comment (by steve@…):

 My point is though that even when generating generic code with run-time
 detection it's inappropriate to override -march. If generic code is
 required -march can be used to specify a generic target (such as x86_64,
 or i686) and then use feature -m switches.  If building not building
 generic code, it should generally be constrained to the specific set of
 enabled features, and certainly shouldn't override the per target code
 generation optimization.  The GCC bug recommends using
 __attribute__(target("...")) which allows specific functions to use
 features not necessarily available for the given -march, and which doesn't
 fail for LTO, and actually produces the desired behaviour.  See:
 https://gcc.gnu.org/onlinedocs/gcc/Function-Specific-Option-Pragmas.html

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/9766#comment:19>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.