Horrendously bad ARM codegen

Horrendously bad ARM codegen

Does anyone know anything about how to improve this?

Comments

  1. We are investigating the issue. In short, it depends on the potential mis-alignment (to 32 boundary) of the Integer referenced by a pointer. Need a little more time to have all of the answers... and a plan to address this.

    ReplyDelete

Post a Comment