On 17/11/15 12:58, Kyrill Tkachov wrote:
Hi Ramana,
On 17/11/15 12:02, Ramana Radhakrishnan wrote:
On 06/11/15 10:46, Kyrill Tkachov wrote:
Hi all,
In this wrong-code PR the vector setmem expansion and
arm_block_set_aligned_vect in particular
use the wrong offset when calling adjust_automo
Hi Ramana,
On 17/11/15 12:02, Ramana Radhakrishnan wrote:
On 06/11/15 10:46, Kyrill Tkachov wrote:
Hi all,
In this wrong-code PR the vector setmem expansion and
arm_block_set_aligned_vect in particular
use the wrong offset when calling adjust_automodify_address. In the attached
testcase dur
On 06/11/15 10:46, Kyrill Tkachov wrote:
> Hi all,
>
> In this wrong-code PR the vector setmem expansion and
> arm_block_set_aligned_vect in particular
> use the wrong offset when calling adjust_automodify_address. In the attached
> testcase during the
> initial zeroing out we get two V16QI st
Ping.
https://gcc.gnu.org/ml/gcc-patches/2015-11/msg00581.html
Thanks,
Kyrill
On 06/11/15 10:46, Kyrill Tkachov wrote:
Hi all,
In this wrong-code PR the vector setmem expansion and
arm_block_set_aligned_vect in particular
use the wrong offset when calling adjust_automodify_address. In the atta
On 06/11/15 10:46, Kyrill Tkachov wrote:
Hi all,
In this wrong-code PR the vector setmem expansion and
arm_block_set_aligned_vect in particular
use the wrong offset when calling adjust_automodify_address. In the attached
testcase during the
initial zeroing out we get two V16QI stores, but the
