search for: dagarg

...'s safe to lock in as a concept since the match step needs to tell the apply step what it matched. > > The other bit that gets locked in is that the contents of these sections must fit within tblgen's 'dag' syntax. That doesn't seem like much of a burden as code blocks and DagArg/DagArgList (https://llvm.org/docs/TableGen/LangRef.html#values) are very lenient about their contents. The operator DagArg can be any def within tablegen and different backends can act on those defs as they see fit. > > The idea of sharing code between InstCombine and MIR for combines that ma...

Hi Daniel, Thanks for the reply! Le lun. 26 nov. 2018 à 10:00, Daniel Sanders <daniel_l_sanders at apple.com> a écrit : > > Hi Quentin, > > Sorry for the slow reply. > > > On Nov 16, 2018, at 09:25, Quentin Colombet <quentin.colombet at gmail.com> wrote: > > > > Hi Daniel, > > > > I finally read the proposal. > > > > I have a

...lock in as a concept since the match step needs to tell the apply > step what it matched. > > The other bit that gets locked in is that the contents of these sections > must fit within tblgen's 'dag' syntax. That doesn't seem like much of a > burden as code blocks and DagArg/DagArgList ( > https://llvm.org/docs/TableGen/LangRef.html#values) are very lenient > about their contents. The operator DagArg can be any def within tablegen > and different backends can act on those defs as they see fit. > > The idea of sharing code between InstCombine and MIR for...