On Thu, 2009-07-23 at 11:14 -0700, Zack Rusin wrote: > On Thursday 23 July 2009 13:58:54 Keith Whitwell wrote: > > > OK. I wanted to fix any breakages from my recent changes, so > > > trivial/tri is at least running now. > > > > BTW - I don't think this should be removed from master - there are a lot > > of people just waiting to get a bit of time to work on this, myself > > included... > > IMHO this should be done on a feature branch. As it stands we just have code > in there that's obviously broken and while a lot of people would love to work > on it no one has the time right now. And fixing things that will need to be > redone seems rather counterproductive.
> Before anything else the problem of representation needs to solved. The two > step approach that the code in there started on using is again, imho, by far > the best but it likely needs a solid discussion to get everyone on the same > page. I don't think that representation is such a big problem. IMO, gallivm should be just a library of TGSI -> LLVM IR building blocks. For example, the class Instruction should be all virtuals, and a pipe driver would override the methods it wants. LLVM IR -> hardware assembly backend would then be necessary. If a hardware has higher level statements which are not part of LLVM IR, then it should override and generate the intrinsics itself, or even better, generate asm statements directly from those methods. Currently, my main interest for LLVM is to speed up softpipe with the TGSI -> SSE2 translation. I'd like to code generate with LLVM the whole function to rasterize and render a triangle (texture sampling, fragment shading, blending, etc). I'm not particular worried about the representation as vanilla LLVM can already represent almost everything needed. Jose ------------------------------------------------------------------------------ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
