On Fri, Oct 3, 2014 at 8:52 AM, Jakub Jelinek <ja...@redhat.com> wrote:
>> Tested with >> GCC_TEST_RUN_EXPENSIVE=1 make -k check-gcc \ >> RUNTESTFLAGS='--target_board=unix/-mavx2 dg-torture.exp=vshuf*.c' >> on x86_64-linux, ok for trunk if it passes bootstrap? >> >> As for the previous testcase with distilled pr52252-atom.c permutations, >> f1/f4 is now vpunpcklbw/vpunpckhbw/vperm2i128, f2 2x vpshufb/vpermq/vpor, >> f3/f5/f6 vperm2i128/vpalignr, suggestions how to improve that? >> >> 2014-10-02 Jakub Jelinek <ja...@redhat.com> >> >> PR target/62128 >> * config/i386/i386.c (expand_vec_perm_palignr): If op1, op0 order >> of palignr arguments can't be used due to min 0 or max - min >> too high, try also op0, op1 order of palignr arguments. >> >> * gcc.dg/torture/vshuf-16.inc (TESTS): Add 2 new permutations. >> * gcc.dg/torture/vshuf-32.inc (TESTS): Add 5 new permutations. > > Now successfully bootstrapped/regtested on x86_64-linux and i686-linux > (without ada, as that doesn't bootstrap right now, Honza is looking into > that). Ok for trunk? OK. Thanks, Uros.