<div dir="ltr">Your proposed changes looks like it undoes the following:<br><a href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20141215/249076.html">http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20141215/249076.html</a><div>?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 20, 2015 at 12:27 PM, Rafael EspĂ­ndola <span dir="ltr"><<a href="mailto:rafael.espindola@gmail.com" target="_blank">rafael.espindola@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When going via assembly a lock prefix becomes a LOCK_PREFIX<br>
instruction before the rest of the instruction.<br>
<br>
With direct object emission it remains a prefix. It is not clear why<br>
it is not expanded in two MCInst, but we should at least print the<br>
lock prefix first to get the same binary output.<br>
<br>
Cheers,<br>
Rafael<br>
<br>_______________________________________________<br>
llvm-commits mailing list<br>
<a href="mailto:llvm-commits@cs.uiuc.edu">llvm-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a><br>
<br></blockquote></div><br></div>