[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gas/6518] wrong diagnostic for movsx/movzx/vcvtpd2dq/vcvtpd2ps/vcvt
From: |
jbeulich at novell dot com |
Subject: |
[Bug gas/6518] wrong diagnostic for movsx/movzx/vcvtpd2dq/vcvtpd2ps/vcvttpd2dq |
Date: |
26 May 2008 08:47:11 -0000 |
------- Additional Comments From jbeulich at novell dot com 2008-05-26 08:47
-------
I disagree to this approach of fixing the issue - for one, the existing
diagnostic shouldn't become more vague for cases it was precise for
so far, and secondly in other cases operand size ambiguity is being
reported correctly:
.intel_syntax noprefix
.text
Start:
vcvtpd2ps xmm0, [eax]
vcvtpd2ps xmm0, xmmword ptr [eax]
vcvtpd2ps xmm0, ymmword ptr [eax]
movzx eax, [eax]
movzx eax, byte ptr [eax]
movzx eax, word ptr [eax]
add [eax], 1
add byte ptr [eax], 1
add word ptr [eax], 1
add dword ptr [eax], 1
mov [eax], 1
mov byte ptr [eax], 1
mov word ptr [eax], 1
mov dword ptr [eax], 1
You'll note that for movzx the same problem as for the three newly
added AVX instructions exists, so this (and then obviously movsx) is
another candidate needing proper fixing - it properly showed the
"ambiguous operand size" message in 2.18, so I'm afraid this is
another regression introduced by some of the large re-work you did
(the code is still there, at around tc-i386.c:2700, but presumably
isn't being reached anymore).
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
Summary|wrong diagnostic for |wrong diagnostic for
|vcvtpd2dq/vcvtpd2ps/vcvttpd2|movsx/movzx/vcvtpd2dq/vcvtpd
|dq |2ps/vcvttpd2dq
http://sourceware.org/bugzilla/show_bug.cgi?id=6518
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.