Marcus Shawcroft wrote:
On 30 January 2015 at 12:09, Alan Lawrence wrote:
This was posted towards the end of stage 3, a few days before stage 4
started. Is it now too late to "ping" ?
--Alan
gcc/ChangeLog:
* config/aarch64/arm_neon.h (vst1_lane_f32, vst1_lane_f64,
vst1_lane
On 30 January 2015 at 12:09, Alan Lawrence wrote:
> This was posted towards the end of stage 3, a few days before stage 4
> started. Is it now too late to "ping" ?
>
> --Alan
>> gcc/ChangeLog:
>>
>> * config/aarch64/arm_neon.h (vst1_lane_f32, vst1_lane_f64,
>> vst1_lane_p8, vst1_l
This was posted towards the end of stage 3, a few days before stage 4
started. Is it now too late to "ping" ?
--Alan
Alan Lawrence wrote:
Nowadays, just storing the (bigendian-corrected) vector element to the address,
generates exactly the same assembler for all cases except
{float,int,uint}6
Nowadays, just storing the (bigendian-corrected) vector element to the address,
generates exactly the same assembler for all cases except
{float,int,uint}64x1_t, where
st1 {v0.d}[0], [x0]
becomes
str d0, [x0]
This is not a problem, and the change will be much better for optimization
through th
