[Octave-bug-tracker] [bug #66882] Convolution code path improvements

[Markus Mützel]

Follow-up Comment #68, bug #66882 (group octave):

It might also be that Clang handles `std::complex<float>` different from
`double _Complex` in that respect. But GCC does not.

In principle, they *are* different types. So, Clang might not be wrong
here...

Maybe, we should use `FloatComplex *` and `Complex *` in the function
declarations of the C++ wrapper functions and reinterpret_cast these pointers
to `F77_CMPLX *` and `F77_DBLE_CMPLX *` when calling the ?axpy Fortran
functions?

That is a bit risky if the alignment of these type would indeed be different.
But that is not a new "risk" that would be introduced by that change. These
pointers have always been converted between each other one way or the other.
And we didn't have issues so far...


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66882>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature