<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - wrong color in flightgear for the c172p if "Atmospheric light scattering" is used" href="https://bugs.freedesktop.org/show_bug.cgi?id=81500#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - wrong color in flightgear for the c172p if "Atmospheric light scattering" is used" href="https://bugs.freedesktop.org/show_bug.cgi?id=81500">bug 81500</a> from <a class="email" href="mailto:mister.freeman@laposte.net" title="Barto <mister.freeman@laposte.net>"> Barto</a> <pre>(In reply to <a href="show_bug.cgi?id=81500#c22">comment #22</a>) > From what I can see, this commit has nothing to do with any issues > introduced by the originally bad commit... this will require some > investigation. > Could it be a gcc issue ? I use gcc 4.9.0 20140604 (prerelease) with archlinux 64 bits, maybe some lines in commit d030a3404ca0fedf365cb0fd41eaad7abc8ff132 trigger a weird bug in gcc during compilation, and maybe commit 1d9f74eda75da05b4d5c7df5fc1e6f5ab8d88322 restores a correct behaviour from gcc ( this commit changes something in /src/glsl/Makefile.sources ) another explanation is that some functions in /src/glsl/link_varyings.cpp are sometimes disabled by changes made by commit 1d9f74eda75da05b4d5c7df5fc1e6f5ab8d88322, the faulty function may never been called, which prevent the bug ( cessna C172P in green if an ati radeon HD4650 is used and ""Atmospheric light scattering" option enabled in flightgear ), I could use a debug version of mesa in order to see if some functions in /src/glsl/link_varyings.cpp are really called if commit 1d9f74eda75da05b4d5c7df5fc1e6f5ab8d88322 is used, I think there is probably a side effect elsewhere with this commit which cancels the bug ( and may create another bugs undiscovered for now )</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>