-
Key: VSIPL16-8
-
Legacy Issue Number: 18203
-
Status: open
-
Source: dpdx.net ( Brooks Moses)
-
Summary:
The specification defines complex_i as "The implementation shall define
this type to be complex<short>, complex<int>, or complex<long int> such
that the choice of underlying type is the same as scalar_i."This is problematic, because the C++ spec states that complex<T> is not
necessarily defined when T is not float or double. In practice, GCC
provides only incomplete definitions for the int/short/long cases.Since cscalar_i is only used in a very few places, I suggest that it
should simply be removed from the spec.(The changelog in the back of the document mentions a change related to
this, but the actual text does not appear to be changed.) -
Reported: VSIPL++ 1.2 — Tue, 23 Oct 2012 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
VSIPL16 — VSIPL++ spec references nonexistent complex types
- Key: VSIPL16-8
- OMG Task Force: Vector Image Signal Processing Specifications 1.6 RTF