Displaying 6 results from an estimated 6 matches for "allowselementalignedneon".
2012 Sep 06
0
[LLVMdev] Unaligned vector memory access for ARM/NEON.
...ect code setup in ARMSubtarget to
accurately represent this table. I would propose that we keep the existing
field for unaligned access and add a new field for element-aligned access.
The AllowsUnAlignedMem field remains as is and it could be used to represent
the SCTLR.A column in Table A3-1. The AllowsElementAlignedNEON field would
be used allow targets to generate vld1/vst1 instructions for element-aligned
accesses. By default it would be set to true for armv7 targets with NEON.
The -arm-strict-align would set both of the fields to false. This would
retain the behavior that seems to be desired from the
test/Code...
2012 Sep 06
2
[LLVMdev] Unaligned vector memory access for ARM/NEON.
...arget to
> accurately represent this table. I would propose that we keep the existing
> field for unaligned access and add a new field for element-aligned access.
>
> The AllowsUnAlignedMem field remains as is and it could be used to represent
> the SCTLR.A column in Table A3-1. The AllowsElementAlignedNEON field would
> be used allow targets to generate vld1/vst1 instructions for element-aligned
> accesses. By default it would be set to true for armv7 targets with NEON.
That doesn't make sense to me. Element-aligned Neon load/stores are always valid. The AllowsUnalignedMem setting is sup...
2012 Sep 06
2
[LLVMdev] Unaligned vector memory access for ARM/NEON.
Hello,
Thanks again. We did try overestimating the alignment, and saw the vldr
you reference here.
It looks like a recent change (r161962?) did enable vld1 generation for
this case (great!) on darwin, but not linux.
I'm not sure if the effect of lowering load <4 x i16>* align 2 to
vld1.16 this was intentional in this change or not.
If so, my question is what is the preferable way to
2012 Sep 06
0
[LLVMdev] Unaligned vector memory access for ARM/NEON.
...et to accurately represent this table. I would propose that
> we keep the existing field for unaligned access and add a new field for
element-aligned access.
>
> The AllowsUnAlignedMem field remains as is and it could be used to
> represent the SCTLR.A column in Table A3-1. The
> AllowsElementAlignedNEON field would be used allow targets to generate
> vld1/vst1 instructions for element-aligned accesses. By default it would
be set to true for armv7 targets with NEON.
That doesn't make sense to me. Element-aligned Neon load/stores are always
valid. The AllowsUnalignedMem setting is suppose...
2012 Sep 07
2
[LLVMdev] Unaligned vector memory access for ARM/NEON.
...t this table. I would propose that
>> we keep the existing field for unaligned access and add a new field for
> element-aligned access.
>>
>> The AllowsUnAlignedMem field remains as is and it could be used to
>> represent the SCTLR.A column in Table A3-1. The
>> AllowsElementAlignedNEON field would be used allow targets to generate
>> vld1/vst1 instructions for element-aligned accesses. By default it would
> be set to true for armv7 targets with NEON.
>
> That doesn't make sense to me. Element-aligned Neon load/stores are always
> valid. The AllowsUnalign...
2012 Sep 07
0
[LLVMdev] Unaligned vector memory access for ARM/NEON.
...>> we keep the existing field for unaligned access and add a new field
> >> for
> > element-aligned access.
> >>
> >> The AllowsUnAlignedMem field remains as is and it could be used to
> >> represent the SCTLR.A column in Table A3-1. The
> >> AllowsElementAlignedNEON field would be used allow targets to
> >> generate
> >> vld1/vst1 instructions for element-aligned accesses. By default it
> >> would
> > be set to true for armv7 targets with NEON.
> >
> > That doesn't make sense to me. Element-aligned Neon load/st...