On Feb 28, 2012, at 6:36 AM, Don Thompson wrote:
Have the vDSP functions vDSP_vabs and vDSP_vabsD recently changed?
They seem to be no longer working other than to simply return an
unchanged version of an input.
Here is a simple, Cocoa test routine I used to prove the point:
unsigned int ii;
double aa[10], bb[10];
for( ii=0; ii<10; ii++ ) { aa[ii]=1.1, bb[ii]=0; }
aa[1]=aa[3]=aa[6]=-2.2;
vDSP_vabsD( aa, 1, bb, 1, 10 );
ii = 0;
with breakpoints set at the "aa[1] ..." and "ii=0" lines.
The aa array is as expected at the 1st breakpoint; unfortunately, at
the 2nd breakpoint, the bb array matches aa rather than an absolute
value version of aa.
This is a question for the performance-dev list.
Does the problem go away if you malloc the arrays?
Jan E.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
