<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Implement SSBOs in GLSL front-end and i965" href="https://bugs.freedesktop.org/show_bug.cgi?id=89597#c42">Comment # 42</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Implement SSBOs in GLSL front-end and i965" href="https://bugs.freedesktop.org/show_bug.cgi?id=89597">bug 89597</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>(In reply to Francisco Jerez from <a href="show_bug.cgi?id=89597#c38">comment #38</a>) > (In reply to Iago Toral from <a href="show_bug.cgi?id=89597#c37">comment #37</a>) > > If that is not a good idea, then I guess the alternative would be to do it > > the other way around: fix the dispatch mask in the read/write messages to be > > like the pixel mask we use in atomic operations, but I don't know if that is > > possible. > > AFAIK scattered DWORD read and write messages don't to take a > sample mask independent from the execution mask. It seems to me > that they aren't particularly well-suited for this extension. > Is there any reason you aren't using untyped surface reads and > writes instead? That would allow you to provide an explicit > sample mask, share some code with ARB_shader_image_load_store by > using the same instructions (I'll land my patches adding support > for untyped surface writes shortly), and access up to 128 bits of > data per channel and message, likely giving better performance in > the long run. I'll take the blame for that. I'm not nearly as familiar with the image read/write instructions as you are (having worked on load_store) and I wasn't thinking about pixel masks at the time. I previously used the scattered read/write instructions for doing spilling on registers with indirects which is why I suggested them. It certainly sounds like the untyped image read/write instructions are better suited for the task.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>