On Mon, Jul 9, 2012 at 1:55 AM, Knut Petersen wrote:
> Søren, the bad commit was supposed to fix a gcc -O0 compile problem, but it
> breaks
> gcc -O0 compilation here. Reverting f9c91ee2 fixes the problem for me.
Is this build automated?
If it's an automated build that runs the test suite, you'r
On Mon, Jul 9, 2012 at 7:31 AM, Søren Sandmann wrote:
> From: Søren Sandmann Pedersen
>
> When not optimizing, write _mm_shuffle_pi16() as a statement
> expression with inline assembly. That way we avoid
> __builtin_ia32_pshufw(), which is only available when compiling with
> -msse, while still a
That compiles cleanly here.
Tested-by: Knut Petersen
From: Søren Sandmann Pedersen
When not optimizing, write _mm_shuffle_pi16() as a statement
expression with inline assembly. That way we avoid
__builtin_ia32_pshufw(), which is only available when compiling with
-msse, while still allowing
From: Søren Sandmann Pedersen
When not optimizing, write _mm_shuffle_pi16() as a statement
expression with inline assembly. That way we avoid
__builtin_ia32_pshufw(), which is only available when compiling with
-msse, while still allowing the non-optimizing gcc to understand that
the second argum
Knut Petersen writes:
> Søren, the bad commit was supposed to fix a gcc -O0 compile problem, but it
> breaks
> gcc -O0 compilation here. Reverting f9c91ee2 fixes the problem for me.
Thanks for the bug report. Can you please try the following patch and
let me know if it fixes the problem?
Sore
