Ok, thanks Charles - sorry for/if duplication of effort, that just spun out of
trying to get rid of the calls to aarch64_simd_lane_bounds, as per
https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02510.html . Again as per that
message I'm leaving aarch64_ld{2,3,4}_lane to you ;).
Also there is the
On 5 December 2014 at 11:45, Alan Lawrence wrote:
> Following on from Charles Baylis' patch to improve the error message when
> expanding arguments with qualifier_lane_index, this applies similar
> treatment to __builtin_aarch64_im_lane_boundsi (using for e.g. vset_lane and
> vext), and the more g
Following on from Charles Baylis' patch to improve the error message when
expanding arguments with qualifier_lane_index, this applies similar treatment to
__builtin_aarch64_im_lane_boundsi (using for e.g. vset_lane and vext), and the
more general case of immediates which should be constant but a
