Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Patch is updated according to latest upstream version. Updated licenses, added CFI encoding for Xtensa target
Patch is updated according to LLVM upstream version and latest Xtensa backend version.
llvm/lib/Target/Xtensa/MCTargetDesc/XtensaAsmBackend.cpp | ||
---|---|---|
91 | This should maybe be a report_fatal_error? llvm_unreachable will be optimized out of release builds so if this is something a user can trigger the fatal error would be better. | |
llvm/lib/Target/Xtensa/MCTargetDesc/XtensaMCCodeEmitter.cpp | ||
16 | I think this typically comes after the includes | |
87 | maybe fatal_error? |
Correct instruction descriptions, format descriptions and instruction operands according to common style for *.td files. The llvm_unreachable is substituted to report_fatal_error.
As this is primarily boilerplate, mostly looks good. Just one minor fix.
llvm/lib/Target/Xtensa/MCTargetDesc/XtensaAsmBackend.cpp | ||
---|---|---|
106 | I would use the nop.n encoding here (0xF03D). Then on density machines, the only situation with an invalid instruction is the single-byte case. Although bonus points for a little bit of math to make every case but the single-byte case work--that would be best. |
llvm/lib/Target/Xtensa/MCTargetDesc/XtensaAsmBackend.cpp | ||
---|---|---|
106 | Corrected |
Hi everyone. Since this has been accepted for some time now, we're planning to commit this on Monday (December 16th). Please let us know if there is anything else we should address.
This should maybe be a report_fatal_error? llvm_unreachable will be optimized out of release builds so if this is something a user can trigger the fatal error would be better.