Displaying 2 results from an estimated 2 matches for "riscvinstrinfo_conventional".
2017 Aug 18
5
RFC/bikeshedding: Separation of instruction and pattern definitions in LLVM backends
...r 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 different .td file.
Does anyone have st...
2017 Aug 18
2
RFC/bikeshedding: Separation of instruction and pattern definitions in LLVM backends
...lt;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 out, you
> may
> > want to move...