Be more consistent in the naming convention for the various RET instructions to help prevent future scheduler model mismatches like those that were only addressed in D44687.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Event Timeline
Comment Actions
Not sure if I understand it correct or not. I used to take the number as system mode. E.g., CALL16m, POP32r etc. And W/L/Q as the size of memory operand. Maybe we should change RETL etc. to RET32 instead?
Comment Actions
Wow, I haven't thought we have so many use of the MI opcodes. Maybe I shouldn't have suggested this way :)
Comment Actions
Cheers - I agree - I didn't expect the patch to be so bulky, but still I think it makes sense to get this done once and for all!
clang-format: please reformat the code