<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes])" href="https://bugs.freedesktop.org/show_bug.cgi?id=94900#c29">Comment # 29</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes])" href="https://bugs.freedesktop.org/show_bug.cgi?id=94900">bug 94900</a> from <a class="email" href="mailto:maraeo@gmail.com" title="Marek Olšák <maraeo@gmail.com>"> Marek Olšák</a> <pre>(In reply to Heiko from <a href="show_bug.cgi?id=94900#c28">comment #28</a>) > @Marek, what's the best/usual way to test for performance/instruction count > in mesa changes. I noticed those 'helped'/'hurt'/'+-%' infos and some > runtime numbers in commit messages, but I don't know how they are produced :/ There is no way to get stats for r600g easily. Intel and radeonsi developers use their private shader-db repositories and generate their own stats. Intel have "helped/hurt +-%" stats, while we have much more detailed stats for radeonsi.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>