https://llvm.org/bugs/show_bug.cgi?id=22883
Daniel Sanders <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Daniel Sanders <[email protected]> --- Thanks. I've re-committed with a fix for this in 232165. The main problem was simply that matching operands copied too much of the flag word from their matched operand. As a result, the bits weren't empty (they contained the matched operands' constraint id) and it triggered the assertion. A second problem was that the operand number from a matching operand would be also be used as the constraint id. Matching operands now obtain the constraint id from the matched operand. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
