We can reuse callsShareTOCBase() in some other file to avoid unnecessary nop after the call. The new user of this refactored function will be posted later.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Event Timeline
Comment Actions
This seems like a rather invasive refactoring for removing a nop at -O0. I am not particularly in favour of this. Not only is a nop essentially trivial when it comes to performance (and even code size), but this is restricted to unoptimized code gen for which it isn't really reasonable to expect performant code.