[Bug binutils/24633] objdump accepts invalid encoding for vextractf32x8 (possibly others).

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=24633

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by H.J. Lu <address@hidden>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=12efd68d159444ad8dfe24e49965a228ba980b86

commit 12efd68d159444ad8dfe24e49965a228ba980b86
Author: H.J. Lu <address@hidden>
Date:   Wed Jun 5 10:27:08 2019 -0700

    i386: Check vector length for EVEX vextractfXX and vinsertfXX

    Since not all vector lengths are supported by EVEX vextractfXX and
    vinsertfXX, decode them only with supported vector lengths.

    gas/

        PR binutils/24633
        * testsuite/gas/i386/disassem.s: Add tests for invalid vector
        lengths for EVEX vextractfXX and vinsertfXX.
        * testsuite/gas/i386/x86-64-disassem.s: Likewise.
        * testsuite/gas/i386/disassem.d: Updated.
        * testsuite/gas/i386/x86-64-disassem.d: Likewise.

    opcodes/

        PR binutils/24633
        * i386-dis-evex.h (evex_table): Update EVEX_W_0F3A18_P_2,
        EVEX_W_0F3A19_P_2, EVEX_W_0F3A1A_P_2 and EVEX_W_0F3A1B_P_2.
        (evex_len_table): EVEX_LEN_0F3A18_P_2_W_0,
        EVEX_LEN_0F3A18_P_2_W_1, EVEX_LEN_0F3A19_P_2_W_0,
        EVEX_LEN_0F3A19_P_2_W_1, EVEX_LEN_0F3A1A_P_2_W_0,
        EVEX_LEN_0F3A1A_P_2_W_1, EVEX_LEN_0F3A1B_P_2_W_0,
        EVEX_LEN_0F3A1B_P_2_W_1.
        * i386-dis.c (EVEX_LEN_0F3A18_P_2_W_0): New enum.
        (EVEX_LEN_0F3A18_P_2_W_1): Likewise.
        (EVEX_LEN_0F3A19_P_2_W_0): Likewise.
        (EVEX_LEN_0F3A19_P_2_W_1): Likewise.
        (EVEX_LEN_0F3A1A_P_2_W_0): Likewise.
        (EVEX_LEN_0F3A1A_P_2_W_1): Likewise.
        (EVEX_LEN_0F3A1B_P_2_W_0): Likewise.
        (EVEX_LEN_0F3A1B_P_2_W_1): Likewise.

-- 
You are receiving this mail because:
You are on the CC list for the bug.