Forum > Linux
5.21 source compilable with ICC anywhere?
maverick:
Hi,
Next one is nothing to do with me (because it's em64t), but the error codes are
--- Code: ---vector/analyzeFuncs_x86_64.cpp(76): error: a value of type "__m128" cannot be assigned to an entity of type "x86_m128={__m128}"
zz = _mm_setzero_ps ();
^
vector/analyzeFuncs_x86_64.cpp(120): error: a value of type "__m128d" cannot be assigned to an entity of type "x86_m128d={__m128}"
CC = _mm_loadu_pd (aC);
^
vector/analyzeFuncs_x86_64.cpp(121): error: a value of type "__m128d" cannot be assigned to an entity of type "x86_m128d={__m128}"
DD = _mm_loadu_pd (aD);
^
vector/analyzeFuncs_x86_64.cpp(123): error: argument of type "x86_m128d={__m128}" is incompatible with p!bameter of type "__m128d"
cc = _mm_cvtpd_ps (CC);
^
--- End code ---
I'm thinking of deleting this one. The first
#if defined(__i386__) || defined(__x86_64__) || defined (_M_AMD64) || defined(_M_IX86)
is the problem. May I trim it to
#if defined(__x86_64__) || defined (_M_AMD64) ?
Josef W. Segur:
Eric included the (__i386__) in that sequence, maybe for a good reason I don't understand. I suggest an && !defined (__INTEL_COMPILER) approach.
That chirp method is glacially slow anyhow, at least on my Intel based systems. And if a compiler actually restricted the time and ang variables to single precision float it would be unacceptably inaccurate (as used, calculations involving those will almost certainly be kept in FPU registers and be OK).
Joe
maverick:
Thanks.
I compiled and ran it, but it gives computation errors....I must have done something wrong or it's not ready yet.... Anyway I'd better use source 2.4 here (I've been using s@h's nightly tarball).
Just a moment. There is an intel compiler for em64t.... :D
Navigation
[0] Message Index
[*] Previous page
Go to full version