You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ llvm/buildDA/bin/llc -O3 test.ll
Assertion failed: (Bits != 0 && "Cannot print this instruction."), function printInstruction, file llvm/buildDA/lib/Target/X86/X86GenAsmWriter.inc, line 46606.
Stack dump:
0. Program arguments: llvm/buildDA/bin/llc -O3 tmp.ll
Running pass 'Function Pass Manager' on module 'tmp.ll'.
Running pass 'X86 Assembly / Object Emitter' on function '@test'
Problem happens when we are trying to print "PATCHABLE_OP 2, KILL, <ops...>"
"X86AsmPrinter::LowerPATCHABLE_OP" can't handle target independent opcodes.
Problematic instruction is generated from PatchableFunction.cpp. It looks for the first instruction which in this case turns out to be KILL. I suspect that http://reviews.llvm.org/rL274952 is indirectly responsible for such behaviour.
The text was updated successfully, but these errors were encountered:
I put a first fix in r275278. We may want to clean this up in the long run by introducing an actual MCInstrDesc flag for pseudo instructions that won't generate machine instructions.
lldb: libedit produces garbled, unusable input on Linux
Apply patch from Christos Zoulas, upstream libedit developer.
It has been tested on NetBSD/amd64.
New code supports combination of wide libedit and disabled
LLDB_EDITLINE_USE_WCHAR, which was the popular case on Linux
systems.
llvm-svn: 303907
Extended Description
$ llvm/buildDA/bin/llc -O3 test.ll
Assertion failed: (Bits != 0 && "Cannot print this instruction."), function printInstruction, file llvm/buildDA/lib/Target/X86/X86GenAsmWriter.inc, line 46606.
Stack dump:
0. Program arguments: llvm/buildDA/bin/llc -O3 tmp.ll
Problem happens when we are trying to print "PATCHABLE_OP 2, KILL, <ops...>"
"X86AsmPrinter::LowerPATCHABLE_OP" can't handle target independent opcodes.
Problematic instruction is generated from PatchableFunction.cpp. It looks for the first instruction which in this case turns out to be KILL. I suspect that http://reviews.llvm.org/rL274952 is indirectly responsible for such behaviour.
The text was updated successfully, but these errors were encountered: