[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 Nicolai Hähnle changed: What|Removed |Added Resolution|--- |FIXED

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #70 from bellamort...@gmail.com --- Understood. Thank you for putting in the extra work to make this happen, it's much appreciated. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #69 from Nicolai Hähnle --- bellamorte, feel free to bring this issue to the attention of the gcc and Clang people. It's kind of borderline between a bug and a misfeature. The ::visit method was really huge and

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #68 from Felix Schwarz --- (In reply to higuita from comment #67) > May i suggest to include this patch in any maintenance/bugfix release for > mesa 11.x? in linked patch (see patchwork link above)

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #67 from higu...@gmx.net --- May i suggest to include this patch in any maintenance/bugfix release for mesa 11.x? this would help pushing this to distros updates and to normal linux users and not have to wait 6+ months for the

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #66 from bellamort...@gmail.com --- Let me get this straight, they refused to fix the optimization bug so you were forced to work around it? -- You are receiving this mail because: You are the QA Contact for the bug. You are the

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #65 from Nicolai Hähnle --- Probably nothing :) This patch will likely fix the problem: https://patchwork.freedesktop.org/patch/83779/ -- You are receiving this mail because: You are the QA Contact for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #64 from higu...@gmx.net --- So what a non-programmer user can do to help having this fixed? I have recompiled mesa to workaround this, but many other people have this problem and can't/don't know recompile mesa. I can ask Gaijin

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #63 from Michel Dänzer --- (In reply to Iaroslav Andrusyak from comment #61) > Works for me with aces -safe and with any settings but without shadows > enabled, with shadows i got > >

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #62 from Nicolai Hähnle --- Hi Iaroslav, do you have an apitrace with shadows enabled that triggers the assertion? -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #61 from Iaroslav Andrusyak --- hd 7790 mesa-git Works for me with aces -safe and with any settings but without shadows enabled, with shadows i got state_tracker/st_cb_fbo.c:431:st_update_renderbuffer_surface:

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 higu...@gmx.net changed: What|Removed |Added CC||higu...@gmx.net -- You are receiving

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #60 from higu...@gmx.net --- Created attachment 122976 --> https://bugs.freedesktop.org/attachment.cgi?id=122976=edit apitrace using radeon Using ubuntu 15.10 with oibaf PPA, we get the crash using the intel and the radeon drivers.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #59 from har...@gmx.de --- ... sorry, i have to admit: My last comment is incorrect, there is still a crash with latest mesa git and latest War-Thunder client. (i was testing earlier builds in different directory, without being

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #58 from har...@gmx.de --- This bug seems no longer present. Building latest mesa from git with default settings (-O2), result in a driver working flawless with latest War-Thunder now. -- You are receiving this mail because: You

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 Konstantin A. Lepikhov changed: What|Removed |Added CC|

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #57 from Ernst Sjöstrand --- With current git I get a crash like this: 0x726ff349 in glsl_to_tgsi_visitor::visit (this=0x7fffa2725600, ir=0x7fffa271baf8) at state_tracker/st_glsl_to_tgsi.cpp:3161 3161

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #56 from bellamort...@gmail.com --- Still occurs with latest mesa git and llvm. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #54 from Jose Fonseca --- (In reply to Nicolai Hähnle from comment #53) > The 'FBO incomplete' message is something that is often seen with apitrace. > Not sure where it actually comes from, but in other cases it

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #55 from har...@gmx.de --- (In reply to Nicolai Hähnle from comment #53) > The 'FBO incomplete' message is something that is often seen with apitrace. > Not sure where it actually comes from, but in other cases it doesn't cause >

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #52 from bellamort...@gmail.com --- Of course I used the latest mesa git. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #53 from Nicolai Hähnle --- The 'FBO incomplete' message is something that is often seen with apitrace. Not sure where it actually comes from, but in other cases it doesn't cause problems. Do you get a crash when

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #50 from Nicolai Hähnle --- We clearly need more info. Please try with latest Mesa master. Does the crash still depend on compiler optimizations? Have you tried running in Valgrind as Roland suggested? -- You

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #49 from bellamort...@gmail.com --- Still occurs with GCC 5.3 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #51 from har...@gmx.de --- This bug is still present with latest master and still depends on compiler optimization as described. I have done a run with valgrind, but the results are not very helpful, WT is not open source and there

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #48 from higu...@gmx.net --- -O3 -fno-inline-small-functions also works for me -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #47 from higu...@gmx.net --- well, I also having crash in warthunder... i'm using slackware64, kernel 4.3.0 llvm 3.7.0 and mesa 11.1-rc2 and after applying the patch from Bug 92709 to fix the "unsupported call to function ldexpf in

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #45 from har...@gmx.de --- Created attachment 120336 --> https://bugs.freedesktop.org/attachment.cgi?id=120336=edit backtrace with activated -finline-small-functions -- You are receiving this mail because: You are the QA Contact

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #46 from har...@gmx.de --- here is the code from ir.h where it fails: /** * Determine the number of operands used by an expression */ static unsigned int get_num_operands(ir_expression_operation); /** *

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #44 from har...@gmx.de --- (In reply to bellamorte42 from comment #40) > compiling with -O3 -fno-inline-small-functions works. yep, i can confirm that '-finline-small-functions' is the black sheep. -- You are receiving this mail

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #43 from Roland Scheidegger --- (In reply to bellamorte42 from comment #42) > I'm not sure I follow your logic. The code compiles fine on its own. The > code compiles fine under a variety of optimizations. A

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #35 from har...@gmx.de --- I found that only CXXFLAGS do the trick. If i append CXXFLAGS='-O1' to the configure params, WT works flawless. Since 'st_glsl_to_tgsi.cpp' is the only .cpp file in folder 'state_tracker', it seems to make

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #39 from bellamort...@gmail.com --- Ugh, bisection is done. CXXFLAG -finline-small-functions cuases the segfault. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #40 from bellamort...@gmail.com --- compiling with -O3 -fno-inline-small-functions works. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #41 from Roland Scheidegger --- miscompilations are possible but rare, often different compiler options just hide a bug. Did you try running this with valgrind? -- You are receiving this mail because: You are

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #36 from har...@gmx.de --- i can now confirm: Compiling only file 'st_glsl_to_tgsi.cpp' with '-O1' and everything else with default '-O2' works flawless. -- You are receiving this mail because: You are the QA Contact for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #37 from bellamort...@gmail.com --- Confirmed that -O3 CFLAGS and -O1 CXXFLAGS works. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #42 from bellamort...@gmail.com --- I'm not sure I follow your logic. The code compiles fine on its own. The code compiles fine under a variety of optimizations. A single optimization causes a segfault. =it's the codes fault? --

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #38 from har...@gmx.de --- @bellamorte, for better performance of this workaround, you could try the following: 1. make clean 2. generate 'makefile' via 'autogen.sh' with your prefered settings 3. make 4. delete

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #31 from bellamort...@gmail.com --- Sorry, here's the full list. CFLAGS="-march=bdver2 -O1 -pipe -fstack-protector-strong --param=ssp-buffer-size=4" CXXFLAGS="-march=bdver2 -O1 -pipe -fstack-protector-strong --param=ssp-buffer-size=4"

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 Tapani Pälli changed: What|Removed |Added CC|lem...@gmail.com| -- You are receiving

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #34 from Michel Dänzer --- The gcc manual has a list of all -f... options enabled by -O2. You can try bisecting that list to find the individual -f... option which triggers the problem. -- You are receiving this

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #32 from bellamort...@gmail.com --- -fno-strict-aliasing with -O3 still segfaults. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #33 from bellamort...@gmail.com --- -O2 segfaults -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 Michel Dänzer changed: What|Removed |Added Component|Drivers/Gallium/radeonsi|Mesa core

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #29 from bellamort...@gmail.com --- Well that was quick. Not done testing it yet. First test run was done with -march=bdver2 and -O0. That worked. Second one was done with -march=bdver2 and -O1. That worked. Orginally I was using

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

https://bugs.freedesktop.org/show_bug.cgi?id=92850 --- Comment #30 from Michel Dänzer --- Is -fno-strict-aliasing included in the final flags passed to the compiler? If not, does adding that help? -- You are receiving this mail because: You are the QA Contact for the bug.