search for: 0c61ebc131076c6186052c29968a49

...i, Aug 18, 2017 at 5:05 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk > wrote: > On 18 Aug 2017, at 10:55, Alex Bradbury <asb at asbradbury.org> wrote: > > > > I've demonstrated both the "conventional" approach > > <https://gist.github.com/asb/0c61ebc131076c6186052c29968a49 > 1d#file-riscvinstrinfo_conventional-td> > > and the "separate patterns" approach > > <https://gist.github.com/asb/0c61ebc131076c6186052c29968a49 > 1d#file-riscvinstrinfo_separate_pats-td>. > > Obviously once patterns and pseudo-instructions are separated...

...#39;t a complete split between MC-layer and codegen concerns. The Mips{64,32}r6InstrInfo.td does also factor out this information. This seems less compelling to me, but dissenting opinions are welcome! I've demonstrated both the "conventional" approach <https://gist.github.com/asb/0c61ebc131076c6186052c29968a491d#file-riscvinstrinfo_conventional-td> and the "separate patterns" approach <https://gist.github.com/asb/0c61ebc131076c6186052c29968a491d#file-riscvinstrinfo_separate_pats-td>. Obviously once patterns and pseudo-instructions are separated out, you may want to move them to a diffe...