Re: [Boost-bugs] [Boost C++ Libraries] #11756: boost.Test: non standards compliant use of FE_* macros (unable to compile boost test library on FPU-less arches)

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11756: boost.Test: non standards compliant use of FE_* macros (unable to compile boost test library on FPU-less arches)
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2017-03-08 14:52:03

#11756: boost.Test: non standards compliant use of FE_* macros (unable to compile
boost test library on FPU-less arches)
----------------------------------+------------------------
  Reporter:  bartosz.krasinski@…  |      Owner:  renficiaud
      Type:  Patches              |     Status:  reopened
 Milestone:  Boost 1.64.0         |  Component:  test
   Version:  Boost 1.59.0         |   Severity:  Problem
Resolution:                       |   Keywords:
----------------------------------+------------------------

Comment (by André Draszik <git@…>):

 Replying to [comment:37 comment 37]:
 > The way I see this is that there is only 3 options in the code that
 should be handled:
 >
 > * no fpe
 > * seh based fpe
 > * implementation based on fenv (and in that case, not all platforms
 support all signals)

 Basically, there should be 3 options for defining the interface in .hpp,
 but 4 options based on the compilation environment for the .ipp:

 1. no fpe
 2. seh based fpe
 3. implementation based on fenv (and in that case, not all platforms
 support all signals)
  a. using standard C/C++ APIs
  b. using non-standard glibc extensions (feenableexcept() etc.)

 Which is what I meant in [comment:34 comment 34]

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