From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Wed, 23 Dec 2015 15:20:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1402806033==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9140B6E30D for ; Wed, 23 Dec 2015 07:20:42 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1402806033== Content-Type: multipart/alternative; boundary="1450884042.1D6d2.6350"; charset="UTF-8" --1450884042.1D6d2.6350 Date: Wed, 23 Dec 2015 15:20:42 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=80419 --- Comment #92 from Jose Fonseca --- (In reply to Daniel Exner from comment #91) > So it seems like it is indeed a Bug in the game to try to address this index > element but also the operation should not crash and its unspecified > behaviour. > > Perhaps radeonsi should handle it the same as other mesa drivers to for the > sake of cosistency. Yes, crashing should be avoided. But correct rendering, no, not generally. Not unless it can be without performance impact (which is probably not the case.) Otherwise it would be sacrificing the performance of correct GL apps, for the sake of buggy GL apps. Which is rewarding the wrong behavior. It's not that hard: the start/end parameters are hints precisely aimed at enabling the driver to do performance optimizations. If the application developers can't get them right, just them don't set to invalid values! Use 0 / ~0 which is guaranteed to work. This way the application developers that actually bothered to get them right don't get penalized. Everybody's happy. Maybe it would help if Mesa's KHR_debug / apitrace checked for this sort of error. -- You are receiving this mail because: You are the assignee for the bug. --1450884042.1D6d2.6350 Date: Wed, 23 Dec 2015 15:20:42 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 92 on bug 80419 from 
(In reply to Daniel Exner from comment #91)
> So it seems like it is indeed a Bug in the game to try to address this index
> element but also the operation should not crash and its unspecified
> behaviour.
> 
> Perhaps radeonsi should handle it the same as other mesa drivers to for the
> sake of cosistency.

Yes, crashing should be avoided.

But correct rendering, no, not generally.  Not unless it can be without
performance impact (which is probably not the case.)

Otherwise it would be sacrificing the performance of correct GL apps, for the
sake of buggy GL apps.  Which is rewarding the wrong behavior.


It's not that hard: the start/end parameters are hints precisely aimed at
enabling the driver to do performance optimizations.  If the application
developers can't get them right, just them don't set to invalid values!  Use 0
/ ~0 which is guaranteed to work.   This way the application developers that
actually bothered to get them right don't get penalized.  Everybody's happy.


Maybe it would help if Mesa's KHR_debug / apitrace checked for this sort of
error.

You are receiving this mail because:
  • You are the assignee for the bug.
--1450884042.1D6d2.6350-- --===============1402806033== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1402806033==--