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

[Mike Miller]

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

Ugh, so this means Apple is still shipping libc++ at some 3.5 version with
clang 3.6? This should really be fixed by the vendor, how much do we want to
work around Apple's shortcomings?

If we really have to, the supplied patch seems mostly harmless to me, except
it would be much nicer to use a feature test for this failure instead of
applying it unconditionally for all libc++. For example, on my Debian system,
_LIBCPP_VERSION is 1101, but this patch is not needed. So the current #if
condition is not correct for me.

We have a similar check for a bug in some intermediate version of gcc, that
could be adapted to this compiler bug. See OCTAVE_CHECK_BROKEN_STL_ALGO_H in
m4/acinclude.m4. I would like to see something similar if we're going to patch
around this bug in the LLVM libc++.

    _______________________________________________________

Reply to this item at:

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

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