fix out of bounds pointer access when given 1D texture

This started showing up on Dash3 in TestControlPointsHandleItem
a few weeks back. I suspect driver change caused the resample path
to start being exercised there.

Change-Id: I98e9afea200c4b5ccfa44b2523f09590efb9ac35
Merge topic 'fix_1D_texture_resampling' into master

e1982451 fix out of bounds pointer access when given 1D texture