search for: insertat

...Greedy to simply duplicate the trivially rematerializable instruction at every reload site? Perhaps this is something it would need to query the target for? Perhaps Greedy would be able to call something like TargetInstrInfo::rematerializeValue(MachineInstr &RematMI, MachineBasicBlock::iterator InsertAt) or something along those lines? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190220/ca8b7cf5/attachment.html>

...licate the trivially rematerializable instruction at > every reload site? Perhaps this is something it would need to query the > target for? Perhaps Greedy would be able to call something like > TargetInstrInfo::rematerializeValue(MachineInstr &RematMI, > MachineBasicBlock::iterator InsertAt) or something along those lines? > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > -------------- next part -------------- An HTML attachm...

...Greedy to simply duplicate the trivially rematerializable instruction at every reload site? Perhaps this is something it would need to query the target for? Perhaps Greedy would be able to call something like TargetInstrInfo::rematerializeValue(MachineInstr &RematMI, MachineBasicBlock::iterator InsertAt) or something along those lines? > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <https://lists.llvm....

...zable instruction at >>> every reload site? Perhaps this is something it would need to query the >>> target for? Perhaps Greedy would be able to call something like >>> TargetInstrInfo::rematerializeValue(MachineInstr &RematMI, >>> MachineBasicBlock::iterator InsertAt) or something along those lines? >>> > _______________________________________________ >>> > LLVM Developers mailing list >>> > llvm-dev at lists.llvm.org >>> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >>> >>> > __...

...ombine algorithm. > > Controlling the insertion point to address loads like in your example above could be done quite naturally if the MIR is expressed in a DAG: > > def : GICombineRule< > (match (G_LOAD $tmp, $ptr):$load, > (G_SEXT $dst, $tmp)), > (apply (insertat $load), > (G_SEXTLOAD $dst, $ptr))>; This isn't quite the same thing as the extending loads combine in the example. In that combine, it's matching the load and all uses of its result and chosing a replacement based on the global usage of that def across the whole function,...

Hi All, I've been working on the GlobalISel combiner recently and I'd like to share the plan for how Combine Rules will be defined in GlobalISel and solicit feedback on it. This email ended up rather long so: TL;DR: We're planning to define GlobalISel Combine Rules using MIR syntax with a few bits glued on to interface with the algorithm and escape into C++ when we need to.

...the insertion point to address loads like in your example above could be done quite naturally if the MIR is expressed in a DAG: >>> >>> def : GICombineRule< >>> (match (G_LOAD $tmp, $ptr):$load, >>> (G_SEXT $dst, $tmp)), >>> (apply (insertat $load), >>> (G_SEXTLOAD $dst, $ptr))>; >> This isn't quite the same thing as the extending loads combine in the example. In that combine, it's matching the load and all uses of its result and chosing a replacement based on the global usage of that def across the...