(original) (raw)
I probably misunderstood the question. You probably want to do this in SelectionDAG.
On Fri, Oct 21, 2016 at 10:29 AM, Ehsan Amiri <ehsanamiri@gmail.com> wrote:
The correctness question still remains open for me.You can do this by changing instruction scheduling heuristics. I think the more important question is if this correct always for all platforms.I don't know which scheduler you use. We use GenericScheduler and PostGenericScheduler before and after RA. These classes have a ::tryCandidate method which compares two instructions that can be legally scheduled and decide which of the two should be scheduled. Currently these method are target independent.On Thu, Oct 20, 2016 at 8:08 PM, Alex Susu via llvm-dev <llvm-dev@lists.llvm.org> wrote:Hello.
Is there a way to specify in the back end an (ISD::INLINEASM) SDNode to be scheduled first under all circumstances? I need to specify something like node priority to schedule the node before all other nodes in the SelectionDAG of the basic block.
(Using chain or glue edges in order to make a node first is not a good idea, since I am doing this at instruction selection time, on individual nodes.)
Thank you,
Alex
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
LLVM Developers mailing list
llvm-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev