Re: [PATCH] If !-prefer-avx128, prefer using even 32-byte integer vector modes

On Tue, Nov 8, 2011 at 7:44 AM, Jakub Jelinek wrote: > Hi! > > Working virtually out of Pago Pago. > > Is there a reason why we don't prefer 32-byte integer vector modes > even for AVX?  If a vectorized loop needs some operation that is only > supported by AVX2 we would retry whenever seeing such

Re: [PATCH] If !-prefer-avx128, prefer using even 32-byte integer vector modes

On Tue, Nov 8, 2011 at 7:44 AM, Jakub Jelinek wrote: > Working virtually out of Pago Pago. Hm...? > Is there a reason why we don't prefer 32-byte integer vector modes > even for AVX?  If a vectorized loop needs some operation that is only > supported by AVX2 we would retry whenever seeing such

[PATCH] If !-prefer-avx128, prefer using even 32-byte integer vector modes

Hi! Working virtually out of Pago Pago. Is there a reason why we don't prefer 32-byte integer vector modes even for AVX? If a vectorized loop needs some operation that is only supported by AVX2 we would retry whenever seeing such stmt, so what I think this costs us mainly some small amount of ti