aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/IRObjectFile.cpp
diff options
context:
space:
mode:
authorReid Kleckner <reid@kleckner.net>2014-08-26 20:32:34 +0000
committerReid Kleckner <reid@kleckner.net>2014-08-26 20:32:34 +0000
commitf6fb78089060818b4352b540abc44da4f62b95ef (patch)
treedd0ee92e1b7d4de343aae1c41ed4a09bffbd429a /llvm/lib/Object/IRObjectFile.cpp
parenta2a1e53085eb33b2c32728d9b5ebbfb718d95575 (diff)
downloadllvm-f6fb78089060818b4352b540abc44da4f62b95ef.zip
llvm-f6fb78089060818b4352b540abc44da4f62b95ef.tar.gz
llvm-f6fb78089060818b4352b540abc44da4f62b95ef.tar.bz2
MC: Split the x86 asm matcher implementations by dialect
The existing matcher has lots of AT&T assembly dialect assumptions baked into it. In particular, the hack for resolving the size of a memory operand by appending the four most common suffixes doesn't work at all. The Intel assembly dialect mnemonic table has ambiguous entries, so we need to try matching multiple times with different operand sizes, since that's the only way to choose different instruction variants. This makes us more compatible with gas's implementation of Intel assembly syntax. MSVC assumes you want byte-sized operations for the instructions that we reject as ambiguous. Reviewed By: grosbach Differential Revision: http://reviews.llvm.org/D4747 llvm-svn: 216481
Diffstat (limited to 'llvm/lib/Object/IRObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions