Re: [PATCH 01/25] Handle vectors that don't fit in an integer.

2018-11-15 Thread Andrew Stubbs
On 14/09/2018 16:37, Richard Sandiford wrote: diff --git a/gcc/combine.c b/gcc/combine.c index a2649b6..cbf9dae 100644 --- a/gcc/combine.c +++ b/gcc/combine.c @@ -8621,7 +8621,13 @@ gen_lowpart_or_truncate (machine_mode mode, rtx x) { /* Bit-cast X into an integer mode. */

Re: [PATCH 01/25] Handle vectors that don't fit in an integer.

2018-09-14 Thread Richard Sandiford
writes: > GCN vector sizes range between 64 and 512 bytes, none of which have > correspondingly sized integer modes. This breaks a number of assumptions > throughout the compiler, but I don't really want to create modes just for this > purpose. > > Instead, this patch fixes up the cases that I've

Re: [PATCH 01/25] Handle vectors that don't fit in an integer.

2018-09-05 Thread Jakub Jelinek
On Wed, Sep 05, 2018 at 12:48:49PM +0100, a...@codesourcery.com wrote: > +++ b/gcc/combine.c > @@ -8621,7 +8621,13 @@ gen_lowpart_or_truncate (machine_mode mode, rtx x) > { >/* Bit-cast X into an integer mode. */ >if (!SCALAR_INT_MODE_P (GET_MODE (x))) > - x = gen_lowpart

[PATCH 01/25] Handle vectors that don't fit in an integer.

2018-09-05 Thread ams
GCN vector sizes range between 64 and 512 bytes, none of which have correspondingly sized integer modes. This breaks a number of assumptions throughout the compiler, but I don't really want to create modes just for this purpose. Instead, this patch fixes up the cases that I've found, so far, suc