[vsipl++] VSIPL++ Compile Problem
Jules Bergmann
jules at codesourcery.com
Mon Mar 26 13:17:32 UTC 2007
Cook, Joseph J wrote:
> Good Afternoon,
>
> I’m trying to compile the following simple program using Parallel
> VSIPL++ for Mercury mcoe, but I am getting a compile error:
>
>
> #include “vsip/vector.hpp”
> int main()
> {
> vsip::Vector<float> foo(10,2.f);
> vsip::Vector<float> bar(10,2.f);
>
> bar *= foo;
> }
>
> The error I get is on a computer unfortunately inaccessible to e-mail so
> I can’t cut and paste it. A portion of it is:
>
> “incomplete type is not allowed:
> map_type map_;
> …many more lines…complaining about BinaryOperator *= in the last line”
>
> If you cannot replicate this problem, let me know.
Joe,
Thanks for the problem report. I will try to reproduce the error
locally. If there are any file names and line numbers associated with
the message above, that might be helfpul.
This is using the 1.3 release?
> My impression was that even though I am using Parallel VSIPL++,
> declaring a Map for my Vectors was an optional parameter, is this true?
Yes, that is correct. The program above should compile without error.
The only thing that stands out is the library is not being initialized
(there is no "vsip::vsipl" object).
Not initializing the library will not cause a compile-time error (but it
may lead to run-time errors, esp when using the library in parallel).
However, the error "incomplete type" suggests that a definition is not
being included, which may be a result of not including a particular
header file. You might including <vsip/initfin.hpp> (necessary to
initilize the library), and potentially <vsip/parallel.hpp>
-- Jules
--
Jules Bergmann
CodeSourcery
jules at codesourcery.com
(650) 331-3385 x705
More information about the vsipl++
mailing list