feel free to disregard, considering the target audience, but s/Designed for Intel GPUs/Designed for GPUs/ ?
(I mean compared to, say, LLVM, NIR has more passes that are in general useful to GPUs and much of what it misses compared to LLVM seems less useful for GPUs or SIMT processors.. I think for other drivers that do nir->backend (which is not LLVM) we could still get some benefit of adding some non-intel-specific opcodes to NIR, but that is more a matter of other drivers not having typed up the patches than some NIR limitation) BR, -R On Wed, May 16, 2018 at 6:14 PM, Laura Ekstrand <la...@jlekstrand.net> wrote: > https://drive.google.com/file/d/1D0k3-p88xEame5gepJQfIcCyZhG4CAsW/view?usp=sharing > > On Mon, May 14, 2018 at 5:44 PM, Jason Ekstrand <ja...@jlekstrand.net> > wrote: >> >> One more comment: NIR is *not* a stable API. >> >> On Mon, May 14, 2018 at 2:10 PM, Laura Ekstrand <la...@jlekstrand.net> >> wrote: >>> >>> I've made the edits. >>> https://drive.google.com/file/d/1D0k3-p88xEame5gepJQfIcCyZhG4CAsW/view?usp=sharing >>> >>> Thanks. >>> >>> Laura >>> >>> On Fri, May 11, 2018 at 5:07 PM, Jason Ekstrand <ja...@jlekstrand.net> >>> wrote: >>>> >>>> Couple of edits: >>>> >>>> i915: I'd leave the bit about "embedded" out. I don't think it's used >>>> for any new deployments at this point. >>>> >>>> 1965: How about "Implements intel-specific parts of OpenGL entrypoints" >>>> >>>> ISL isn't really for converting between surface formats. A better >>>> one-sentence description would be "A library for computing image sizes and >>>> memory layouts" >>>> >>>> BLORP: How about "blit, clear, and resolve functionality" rather than >>>> "driver functionality" >>>> >>>> NIR: Not really a "front-end" more of an "optimizing middle compiler" >>>> >>>> Looks snazzy though. :-) >>>> >>>> On Thu, May 10, 2018 at 6:19 PM, Laura Ekstrand <la...@jlekstrand.net> >>>> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> I developed the following infographic to inform readers about the >>>>> various parts that make up the Intel Mesa drivers. It is intended to help >>>>> groups inside Intel better understand the open source community, and at >>>>> the >>>>> same time, it helps train newcomers to Mesa in driver architecture. >>>>> >>>>> I haven't put this in a tree yet since it is a combination of a >>>>> LibreOffice Draw document and a binary image file. >>>>> >>>>> Thanks. >>>>> >>>>> Laura >>>>> >>>>> >>>>> https://drive.google.com/file/d/1D0k3-p88xEame5gepJQfIcCyZhG4CAsW/view?usp=sharing >>>>> >>>>> _______________________________________________ >>>>> mesa-dev mailing list >>>>> mesa-dev@lists.freedesktop.org >>>>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev >>>>> >>>> >>> >> > > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
