[Octave-bug-tracker] [bug #43298] LLVM 3.5.0 cannot resolve the pow(octave_int<int>, octave_Int<int>) function overload

[Jordi Gutiérrez Hermoso]

Follow-up Comment #28, bug #43298 (project octave):

I'm not sure that our test coverage is complete. In fact, we know it's not:

http://hydra.nixos.org/build/15885705/download/1/coverage/liboctave/util/oct-inttypes.cc.gcov.html
http://hydra.nixos.org/build/15885705/download/1/coverage/liboctave/util/oct-inttypes.h.gcov.html

(People of the future: these links are not stable. You can find them again
from following the coverage links from here:
http://hydra.nixos.org/jobset/gnu/octave-default#tabs-jobs )

I'm actually surprised that you simply removed *both* double and float
conversions and managed to get it to compile with clang. I would have thought
the double conversion needed to remain. Also note how our tests aren't testing
the pow codepath for single, but this may be unintentionally dead code.

Can you verify in the Octave interpreter that both double(int32(42)) and
single(int32(42)) give you 42? John, can you give of other operations that
would have exercised the double and float octave_int conversions?

The number of failed tests is a bit alarming, but that's a problem for
different bug reports.

    _______________________________________________________

Reply to this item at:

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

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