[Bug gas/23418] Incorrect xmmword is accepted

2018-07-18 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23418 H.J. Lu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug gas/23418] Incorrect xmmword is accepted

2018-07-18 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=23418 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The binutils-2_31-branch branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=01683b308a016c49418aee27241389bd2560e0f1 commit

[Bug gas/23418] Incorrect xmmword is accepted

2018-07-18 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=23418 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=11a322db5c8bc23009e97af30180d6b14d86dbd3 commit

[Bug gas/23418] Incorrect xmmword is accepted

2018-07-17 Thread igor.v.tsimbalist at intel dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23418 --- Comment #3 from bd170260 --- After regxmm, regymm, regzmm were combined into regsimd it's impossible to distinguish if xmmword/ymmword/zmmword can represent a memory reference when operand specification contains SIMD register. For example

[Bug gas/23418] Incorrect xmmword is accepted

2018-07-16 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=23418 --- Comment #2 from H.J. Lu --- vcvtps2uqq has the same issue. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org