On 19/06/17 17:16, James Greenhalgh wrote:
On Fri, Jun 16, 2017 at 11:07:41AM +0100, Kyrill Tkachov wrote:
On 16/06/17 10:07, James Greenhalgh wrote:
On Wed, Jun 14, 2017 at 11:21:30AM +0100, Kyrill Tkachov wrote:
<...>
That movv2di expander is the one in vec-common.md that ends up
On Fri, Jun 16, 2017 at 11:07:41AM +0100, Kyrill Tkachov wrote:
>
> On 16/06/17 10:07, James Greenhalgh wrote:
> >On Wed, Jun 14, 2017 at 11:21:30AM +0100, Kyrill Tkachov wrote:
> >
> > <...>
> >
> >>That movv2di expander is the one in vec-common.md that ends up calling
> >>neon_make_constant.
On 16/06/17 10:07, James Greenhalgh wrote:
On Wed, Jun 14, 2017 at 11:21:30AM +0100, Kyrill Tkachov wrote:
<...>
That movv2di expander is the one in vec-common.md that ends up calling
neon_make_constant. I wonder why const0_rtx passed its predicate check
(that would require a V2DImode
On Wed, Jun 14, 2017 at 11:21:30AM +0100, Kyrill Tkachov wrote:
<...>
> That movv2di expander is the one in vec-common.md that ends up calling
> neon_make_constant. I wonder why const0_rtx passed its predicate check
> (that would require a V2DImode vector of zeroes rather than a const0_rtx).
Hi James,
On 12/06/17 14:57, James Greenhalgh wrote:
Hi,
PR71778 is an ICE when you pass a non-constant argument to an intrinsic
which requires a constant.
This ICE was introduced after we rewrote some of the builtin handling for
Neon intrinsics, the issue is that after throwing an error in
Hi,
PR71778 is an ICE when you pass a non-constant argument to an intrinsic
which requires a constant.
This ICE was introduced after we rewrote some of the builtin handling for
Neon intrinsics, the issue is that after throwing an error in
arm_expand_builtin_args, we return const0_rtx to
