diff options
author | Haochen Jiang <haochen.jiang@intel.com> | 2025-07-15 14:11:37 +0800 |
---|---|---|
committer | Haochen Jiang <haochen.jiang@intel.com> | 2025-07-16 10:43:41 +0800 |
commit | 14c6a06be8e0cdb40262d0b8ae000266d97e74cb (patch) | |
tree | 4584c0e4520d88b3d1455588e9247a3ee468624e /gdb/testsuite/gdb.python/py-cmd-exception.py | |
parent | a80775c9278de10223c8db54b8da7a31cdfa0567 (diff) | |
download | binutils-14c6a06be8e0cdb40262d0b8ae000266d97e74cb.zip binutils-14c6a06be8e0cdb40262d0b8ae000266d97e74cb.tar.gz binutils-14c6a06be8e0cdb40262d0b8ae000266d97e74cb.tar.bz2 |
x86: Decouple AMX-AVX512 from AVX10.2 and imply AVX512F
In ISE058, the AVX10.2 imply is removed from AMX-AVX512. This
leads to re-consideration on the imply for AMX-AVX512.
Since it is using zmm register and using zmm register only, we
need to at least imply AVX512F. AVX512VL is not needed since it
is not using xmm/ymms.
On the other hand, if we imply AVX10.1 for AMX-AVX512, disabling
avx10.1 will lead to disabling AMX-AVX512. This would be a surprise
for users.
Based on the two reasons above, the patch is decoupling AMX-AVX512
from AVX10.2 and imply AVX512F.
opcodes/ChangeLog:
* i386-gen.c: Imply AVX512F instead of AVX10.2.
* i386-init.h: Regenerated.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-cmd-exception.py')
0 files changed, 0 insertions, 0 deletions