search for: movi64imm

Displaying 4 results from an estimated 4 matches for "movi64imm".

Did you mean: movi32imm
2016 Jan 15
3
Help handling opaque AArch64 immediates
Hello LLVM, I'm playing with a new ISD::OPAQUE instruction to make hoisting first class and eliminate a lot of tweaky flag setting/checking around opaque constants. It's going well for the IR and x86, but I now I need to sort out details for all the other targets. To start, can someone please advise on the AAarch64 equivalent of these X86 patterns? // Opaque values become mov immediate
2016 Sep 26
2
[RFC] Register Rematerialization (remat) Extension
...gt; Basically, the target defines a pseudo instruction that encodes this > sequence of instructions and expands it after register allocation. > This is a case by case thing, there is no patch that can be > generalized for other target. > For instance, look at the expansion of AArch64:: MOVi64imm. > The bottom line is, our rematerialization scheme is currently > limited, but I am not sure your proposal get us beyond what we > already support. I might have misunderstood the proposal, but why do you say that? The problem is not limited to constants (as perhaps evidenced by Ivan Baev...
2016 Sep 19
2
[RFC] Register Rematerialization (remat) Extension
On Mon, Sep 19, 2016 at 6:21 PM, James Molloy <james at jamesmolloy.co.uk> wrote: > Hi, > > I've been looking at this myself for ARM, and came up with a much simpler > solution: lower immediate materializations to a post-RA pseudo and expand > the chain of materialization instructions after register allocation / > remat. Remat only sees one instruction with no
2016 Nov 27
5
Extending Register Rematerialization
Hello LLVM Developers, We are working on extending currently available register rematerialization to include cases where sequence of multiple instructions is required to rematerialize a value. We had a discussion on this in community mailing list and link is here: http://lists.llvm.org/pipermail/llvm-dev/2016-September/subject.html#104777 >From the above discussion and studying the code we