[libre-riscv-dev] uniform instruction format

Luke Kenneth Casson Leighton lkcl at lkcl.net
Tue Jun 11 04:59:32 BST 2019


On Tue, Jun 11, 2019 at 3:42 AM Jacob Lifshay <programmerjake at gmail.com> wrote:
>
> On Mon, Jun 10, 2019 at 2:55 AM Luke Kenneth Casson Leighton
> <lkcl at lkcl.net> wrote:
> > > >   remember
> > > > that kazan could do with some attention / progress: you're technically
> > > > the only person with the knowledge on how to develop it.
> > >
> > > yeah, I'm thinking I should add another IR layer, since the algorithm i'm
> > > in the middle of implementing (vectorizer) is really complex and should
> > > probably be split up.
> >
> >  makes you wonder how the other implementors do vulkan, doesn't it?
> Pretty much everyone else does that in HW, rather than at compile
> time, which makes it much easier.

 hmm... makes sense.

> >
> >  btw, texturisation: if much of it can be done "by rote" - i.e. you
> > could write clear instructions to someone else on what to do, then i
> > have access to a team that can help.  do let me know if that would
> > work.
> I'll probably work on getting the basic framework of the texture
> library working next, so others can help implementing all the texture
> formats after I get past the best-done-by-single-person part.

 great.  they'll need paying, and clear specs writing, however they're
USD $300 / month / person, which is an extremely compelling reason to
try using them.

l.



More information about the libre-riscv-dev mailing list