Re: [PATCH 3/3] Handle const_vector in mulv4si3 for pre-sse4.1.

2012-06-19 Thread Uros Bizjak
On Mon, Jun 18, 2012 at 10:06 PM, Richard Henderson wrote: >> Please note that you will probably hit PR33329, this is the reason >> that we expand multiplications after reload. Please see [1] for >> further explanation. There is gcc.target/i386/pr33329.c test to cover >> this issue, but it is not

Re: [PATCH 3/3] Handle const_vector in mulv4si3 for pre-sse4.1.

2012-06-18 Thread Richard Henderson
On 2012-06-17 11:37, Uros Bizjak wrote: > Hello! > > Please note that you will probably hit PR33329, this is the reason > that we expand multiplications after reload. Please see [1] for > further explanation. There is gcc.target/i386/pr33329.c test to cover > this issue, but it is not effective an

Re: [PATCH 3/3] Handle const_vector in mulv4si3 for pre-sse4.1.

2012-06-17 Thread Uros Bizjak
On Sun, Jun 17, 2012 at 8:37 PM, Uros Bizjak wrote: > Hello! > > Please note that you will probably hit PR33329, this is the reason > that we expand multiplications after reload. Please see [1] for > further explanation. There is gcc.target/i386/pr33329.c test to cover > this issue, but it is not

Re: [PATCH 3/3] Handle const_vector in mulv4si3 for pre-sse4.1.

2012-06-17 Thread Uros Bizjak
Hello! Please note that you will probably hit PR33329, this is the reason that we expand multiplications after reload. Please see [1] for further explanation. There is gcc.target/i386/pr33329.c test to cover this issue, but it is not effective anymore since the simplification happens at tree level