aboutsummaryrefslogtreecommitdiff
path: root/clang/unittests/Basic/SourceManagerTest.cpp
diff options
context:
space:
mode:
authorReid Kleckner <reid@kleckner.net>2014-08-27 20:10:38 +0000
committerReid Kleckner <reid@kleckner.net>2014-08-27 20:10:38 +0000
commit7b7a599ac568845446dd9e2f9fe37280a0ef1bfd (patch)
treecfd1dae21f7f72676e131e167c510215b8f14aca /clang/unittests/Basic/SourceManagerTest.cpp
parent2443e706c1886085578b32129765ab69bd115688 (diff)
downloadllvm-7b7a599ac568845446dd9e2f9fe37280a0ef1bfd.zip
llvm-7b7a599ac568845446dd9e2f9fe37280a0ef1bfd.tar.gz
llvm-7b7a599ac568845446dd9e2f9fe37280a0ef1bfd.tar.bz2
X86 MC: Handle instructions like fxsave that match multiple operand sizes
Instructions like 'fxsave' and control flow instructions like 'jne' match any operand size. The loop I added to the Intel syntax matcher assumed that using a different size would give a different instruction. Now it handles the case where we get the same instruction for different memory operand sizes. This also allows us to remove the hack we had for unsized absolute memory operands, because we can successfully match things like 'jnz' without reporting ambiguity. Removing this hack uncovered test case involving 'fadd' that was ambiguous. The memory operand could have been single or double precision. llvm-svn: 216604
Diffstat (limited to 'clang/unittests/Basic/SourceManagerTest.cpp')
0 files changed, 0 insertions, 0 deletions