Naveen N. Rao wrote:
It is then for all back-ends to decide how to use such information to
eliminate unnecessary zero extension code-gen during JIT compilation.

One approach is:
  1. Verifier insert explicit zero extension for those instructions that
     need zero extension.
  2. All JIT back-ends do NOT generate zero extension for sub-register
     write any more.

Is it possible to instead give a hint to the JIT back-ends on the instructions needing zero-extension? That would help in case of architectures that have single/more-optimal instruction for zero extension, compared to having to emit 2 instructions with the current approach.

I just noticed your discussion with Alexei on RFC v1 after posting this. I agree that this can be looked into subsequently -- either a new instruction, or detecting this during JIT.

- Naveen


Reply via email to