[Octave-bug-tracker] [bug #47775] realpow and sparse-xpow.cc-tst fails

[Mike Miller]

Follow-up Comment #7, bug #47775 (project octave):

I think someone should test with gcc 4.8 to see if the presence or absence of
the "-std=gnu++11" option causes the test to pass or fail. I think this could
most easily be done on the stable branch, simply by building stable with
CXX="g++ -std=gnu++11" vs the default of CXX=g++.

If the tests do fail with that option added, then this is the same as bug
#47214. That's the first question to answer.

I can't say whether we care about exact answers, all I can say is that at a
glance this looks like a test that someone intended to be exact, and is exact
with recent versions of the gcc compiler. Maybe some library defect in older
versions of gcc causes the wrong call to be evaluated somewhere, as gcc C++11
compliance was still being worked on, and has since been fixed.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47775>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/