PING^8: [PATCH 00/10] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2020-02-24 Thread H.J. Lu
On Sat, Feb 15, 2020 at 7:26 AM H.J. Lu wrote: > > This patch set was originally submitted in Feb 2019: > > https://gcc.gnu.org/ml/gcc-patches/2019-02/msg01841.html > > I broke it into 10 smaller patches for easy review. > > On x86, when AVX and AVX512 are enabled, vector move instructions can > b

[PATCH 00/10] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2020-02-15 Thread H.J. Lu
This patch set was originally submitted in Feb 2019: https://gcc.gnu.org/ml/gcc-patches/2019-02/msg01841.html I broke it into 10 smaller patches for easy review. On x86, when AVX and AVX512 are enabled, vector move instructions can be encoded with either 2-byte/3-byte VEX (AVX) or 4-byte EVEX (A