[LLVMdev] Instruction dependency in ARM backend

pmon mail pmon.mail at gmail.com
Tue Apr 8 04:42:24 PDT 2014


> You definitely can glue them together.
Do you mean instruction bundling?

I see that sometimes (I guess) some optimization does insert other
instructions between movw+movt pair. Is there a flag to say "don't touch
them"?


On Sun, Apr 6, 2014 at 8:42 PM, Anton Korobeynikov
<anton at korobeynikov.info>wrote:

> Hello
>
> > What should be the right approach to implement this?
> You definitely can glue them together. Alternatively, you can disable
> the generation of movt / movw instruction pairs at all. The latter
> probably looks the better solution give the target weirdness :)
>
> > Is this something I can describe in target description for ARM?
> If you mean .td files, then no. movt / movw pairs is inserted via
> "pseudo instruction expansion pass". Look into
> ARMExpandPseudoInsts.cpp
>
>
> --
> With best regards, Anton Korobeynikov
> Faculty of Mathematics and Mechanics, Saint Petersburg State University
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140408/71f11bfa/attachment.html>


More information about the llvm-dev mailing list