[vsipl++] [patch] Forcing a copy for run-time external data access.

[Jules Bergmann]

Stefan Seefeld wrote:
> The attached patch rewrites the 1D workspaces used to prepare
> data to be 'sent' to the FFT backends. It now uses Jules' new
> rt_extdata harness, to take advantage of the backend's handling
> of split/interleaved, as well as non-unit strides, if possible.
> Now the number of copies of the data blocks should be minimal.
> 
> As I'm still in the process of debugging 2D and M cases,
> I send in this partial patch, in the hope that it is useful
> such as for benchmarking, to make sure the performance is
> at least on par with what it used to be before the redesign.
> 
> Hopefully I'm able to send out more patches later tonight...

Stefan,

This looks good.

I need to check how Rt_extdata handles requests for 1D 
stride_unit_dense.  In general it recongnizes that stride_unit_dense is 
a stricter requirement than stride_unit (i.e. anything that is 
stride_unit_dense is also stride_unit, but not visa-versa).  It should 
make an exception for 1D since there are no higher dimensions.

Alternatively, for 1D data you could just request stride_unit, since 
that is the minimal requirement.

				-- Jules



-- 
Jules Bergmann
CodeSourcery
jules at codesourcery.com
(650) 331-3385 x705