<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [PIGLIT,radeonsi] SIGSEGV for shaders/glsl-fs-inline-explosion" href="https://bugs.freedesktop.org/show_bug.cgi?id=70920#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [PIGLIT,radeonsi] SIGSEGV for shaders/glsl-fs-inline-explosion" href="https://bugs.freedesktop.org/show_bug.cgi?id=70920">bug 70920</a> from <a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> Ian Romanick</a> <pre>The cause has been known since the tests were added in 2010: commit 656cc65b2d3782c078d36342d0deec9886514520 Author: Luca Barbieri <<a href="mailto:luca@luca-barbieri.com">luca@luca-barbieri.com</a>> Date: Mon Sep 6 04:56:05 2010 +0200 add GLSL inlining/unroll limit tests, currently failing The current GLSL compiler inlines everything indiscriminately, and unrolls all loops that have a small iteration count. This is a bad idea, because it can lead to exponential growth of the code, as these test cases illustrate. On a naive implementation (like current Mesa) these tests will attempt to allocate more than 2^64 bytes of RAM, ensuring failure. A smart implementation will instead generate actual calls/loops, and the test passes, since the branch protecting the functions/loops is not taken. Currently they aren't added to any profile since they obviously cause piglit to hang until memory is exhausted, possibly causing lots of swap thrashing.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>