<div dir="ltr">On a related note, <br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 23, 2015 at 2:19 PM, Jason Ekstrand <span dir="ltr"><<a href="mailto:jason@jlekstrand.net" target="_blank">jason@jlekstrand.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Mon, Mar 23, 2015 at 11:19 AM, Bruno Jimenez <<a href="mailto:brunojimen@gmail.com">brunojimen@gmail.com</a>> wrote:<br>
> On Wed, 2015-03-18 at 16:37 -0700, Jason Ekstrand wrote:<br>
>> On Wed, Mar 18, 2015 at 4:27 PM, Connor Abbott <<a href="mailto:cwabbott0@gmail.com">cwabbott0@gmail.com</a>> wrote:<br>
>> > On Wed, Mar 18, 2015 at 2:58 PM, Matt Turner <<a href="mailto:mattst88@gmail.com">mattst88@gmail.com</a>> wrote:<br>
>> >> On Thu, Mar 12, 2015 at 9:46 PM, Matt Turner <<a href="mailto:mattst88@gmail.com">mattst88@gmail.com</a>> wrote:<br>
>> >>> Here are some ideas I think might be reasonable GSoC ideas.<br>
>> >>><br>
>> >>> - GLSL linking in NIR<br>
>> >>> - Would allow us to stop doing optimizations and other expensive<br>
>> >>> things on GLSL IR<br>
>> >><br>
>> >> Ian said this should wait until everything is using NIR so that we<br>
>> >> don't have two linkers. :)<br>
>> ><br>
>> > Yeah, and it also won't make sense to do it until we can get the NIR<br>
>> > optimizations up to par with the GLSL ones so that we can disable all<br>
>> > the GLSL ones after linking and not get a regression. This would<br>
>> > involve porting all the GLSL optimizations to NIR, which now that I<br>
>> > think about it actually seems like a quite doable GSoC project -- it's<br>
>> > a pretty well-defined task and there are lots of little optimizations<br>
>> > to translate so it's easy to make progress, although porting all of<br>
>> > them over might be too much for one summer.<br>
>><br>
>> Yeah, grabbing a handful of optimizations and porting them seems like<br>
>> a good GSoC project to me. There's also the NIR checklist which<br>
>> people could grab stuff off of.<br>
><br>
> Out of curiosity, I know that NIR can be used with the intel drivers<br>
> but, is there a way to test it with gallium?<br>
<br>
</span>i965 is where it's actively tested and known to be working. However,<br>
Eric Anholt has a NIR -> TGSI pass so it could be hacked up to work<br>
with gallium.<br></blockquote><div><br><br>On a related note,<br><br></div><div>Has anyone ported shader-db over to working on R600/RadeonSI/<anything non-intel>? I've been meaning to take a look at the NIR->TGSI pass and see if there's an easy way to hook it up to the radeon drivers, but I wanted to be able to get shader-db up and running on that hardware first so that we could get some before/after numbers (I'm assuming that R600 w/o SB will be the main radeon driver that benefits, but I'd love to be proven wrong).<br><br></div><div>--Aaron<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=""><font color="#888888">--Jason<br>
</font></span><div class=""><div class="h5"><br>
> - Bruno<br>
><br>
>> --Jason<br>
>> _______________________________________________<br>
>> mesa-dev mailing list<br>
>> <a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><br>
>> <a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
><br>
><br>
_______________________________________________<br>
mesa-dev mailing list<br>
<a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/mesa-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
</div></div></blockquote></div><br></div></div>