[llvm-commits] We are selecting a CMP64mi32 instead of a CMP64mi8

Rafael Espindola espindola at google.com
Thu Oct 7 13:15:17 PDT 2010


I am debugging a case where llc + llvm-mc produces different results
from using "llc -filetype=obj". The issues is that for the attached
test llc selects CMP64mi32. This prints as

cmpq	$0, -8(%rsp)

Which gets parsed by llvm-mc as the 8 bit immediate version. Why are
we selecting CMP64mi32? The attached patch fixes this particular
issue, but it would be better if we could this in a less brittle way.

Cheers,
-- 
Rafael Ávila de Espíndola
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch
Type: application/octet-stream
Size: 1546 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20101007/5ba5a9b5/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SparseBitVectorTest.ll
Type: application/octet-stream
Size: 1214 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20101007/5ba5a9b5/attachment-0001.obj>


More information about the llvm-commits mailing list