|
From: | Kefu Chai |
Subject: | [Octave-bug-tracker] [bug #43298] LLVM 3.5.0 cannot resolve the pow(octave_int<int>, octave_Int<int>) function overload |
Date: | Wed, 15 Oct 2014 18:09:49 +0000 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10) AppleWebKit/600.1.25 (KHTML, like Gecko) Version/8.0 Safari/600.1.25 |
Follow-up Comment #27, bug #43298 (project octave): @john the source tree compiles fine with clang 3.5 after removing these conversions. and i ran the tests using `make -C test check`. i have Summary: PASS 11450 FAIL 19 XFAIL 7 SKIPPED 216 @jordi, thanks for your comment. i am the author of the patch. > We test for features. Can you write the corresponding autoconf check? will pull together one. once we are confirmed that to remove the double and float conversion operator does not work out. > but if the bug only happens with an LLVM version that also has C++11 enabled, it may be ok. yes. the libc++'s `pow()` template function implementation uses `std::enable_if` also. so i guess it's safe to use C++11 features in the patch. > the autoconf check would need to verify that C++11 constructs like std::enable_if are available. agreed. maybe the simpler way is to reevaluate if we really need the `octave_int::operator` of double and float. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?43298> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |