<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [i965] Compiler backend uses too much stack with Alien: Isolation" href="https://bugs.freedesktop.org/show_bug.cgi?id=93840#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [i965] Compiler backend uses too much stack with Alien: Isolation" href="https://bugs.freedesktop.org/show_bug.cgi?id=93840">bug 93840</a> from <a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> Ian Romanick</a> <pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=93840#c21">comment #21</a>) > (In reply to Matt Turner from <a href="show_bug.cgi?id=93840#c14">comment #14</a>) > > Created <a href="attachment.cgi?id=126122" name="attach_126122" title="patch">attachment 126122</a> <a href="attachment.cgi?id=126122&action=edit" title="patch">[details]</a> <a href='page.cgi?id=splinter.html&bug=93840&attachment=126122'>[review]</a> [review] [review] > > patch > > > > (In reply to Darius Spitznagel from <a href="show_bug.cgi?id=93840#c1">comment #1</a>) > > > Created <a href="attachment.cgi?id=121746" name="attach_121746" title="Alien: Isolation GDB log">attachment 121746</a> <a href="attachment.cgi?id=121746&action=edit" title="Alien: Isolation GDB log">[details]</a> > > > Alien: Isolation GDB log > > > > The memset() at line 935 of > > a4cff18:src/mesa/drivers/dri/i965/brw_schedule_instructions.cpp is > > > > > memset(last_grf_write, 0, sizeof(last_grf_write)); > > > > The backtrace shows > > > > #1 0x00007fffe79015fe in memset (__len=482688, __ch=0, > > __dest=0x7fffa216e550) at /usr/include/x86_64-linux-gnu/bits/string3.h:84 > > > > __len=482688?! > > In my case with today's Mesa & Alien Isoation: > Thread 17 "WinMain" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7f09cc122700 (LWP 23775)] > __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161 > 161 ../sysdeps/x86_64/multiarch/memset-avx2.S: No such file or directory. > (gdb) bt > #0 __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161 > #1 0x00007f09de059b0c in memset (__len=349056, __ch=0, > __dest=0x7f09cc0c98c0) at /usr/include/x86_64-linux-gnu/bits/string3.h:90 > #2 fs_instruction_scheduler::calculate_deps (this=0x7f09cc11ee90) at > ../../../../../../src/mesa/drivers/dri/i965/brw_schedule_instructions.cpp:991 > > -> 349056 byte memset. > > After applying patch similar to yours, game crashes in startup when compiler > is using another stack array. Eero, are you able to collect the shaders that being compiled when the stack explodes? Matt's suspicion is that there is another bug somewhere that causes things to go sideways. Without seeing the shaders, it's just a guessing game.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>