Using a fatal error is bad for user experience.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Target/X86/AsmParser/X86AsmParser.cpp | ||
---|---|---|
3632 | It seems X86MCCodeEmitter::emitREXPrefix has more detailed check for each form. Especially, the commens says "Emit REX prefix ... 2) non-default operand size". Is it not covered by this case? |
llvm/lib/Target/X86/AsmParser/X86AsmParser.cpp | ||
---|---|---|
3632 | I'm not sure what the difference is between "1) 64-bit instructions" and "2) non-default operand size". I think the form code is just mapping registers to different bits in the REX prefix. I don't think the assembler error needs to care about the exact bits, just that some bit will be affected by the operands. But I might be wrong. |
llvm/lib/Target/X86/AsmParser/X86AsmParser.cpp | ||
---|---|---|
3641 | LG. minor nit: https://llvm.org/docs/CodingStandards.html#error-and-warning-messages the majority of error messages don't end with a period. |
It seems X86MCCodeEmitter::emitREXPrefix has more detailed check for each form. Especially, the commens says "Emit REX prefix ... 2) non-default operand size". Is it not covered by this case?