From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup
Date: Wed, 23 Dec 2015 15:20:42 +0000 [thread overview]
Message-ID: <bug-80419-502-x6KBHNdrO9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-80419-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1266 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=80419
--- Comment #92 from Jose Fonseca <jfonseca@vmware.com> ---
(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.
[-- Attachment #1.2: Type: text/html, Size: 2086 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-23 15:20 UTC|newest]
Thread overview: 167+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 18:30 [Bug 80419] New: XCOM: Enemy Known Causes lockup bugzilla-daemon
2014-06-23 18:35 ` [Bug 80419] XCOM: Enemy Unknown " bugzilla-daemon
2014-06-24 2:53 ` bugzilla-daemon
2014-06-24 4:11 ` bugzilla-daemon
2014-06-24 4:28 ` bugzilla-daemon
2014-06-24 4:29 ` bugzilla-daemon
2014-06-24 4:38 ` bugzilla-daemon
2014-06-24 5:43 ` bugzilla-daemon
2014-06-24 6:27 ` bugzilla-daemon
2014-06-24 12:18 ` bugzilla-daemon
2014-06-24 13:24 ` bugzilla-daemon
2014-06-24 17:20 ` bugzilla-daemon
2014-06-24 17:50 ` bugzilla-daemon
2014-06-24 17:51 ` bugzilla-daemon
2014-06-25 3:49 ` bugzilla-daemon
2014-06-27 8:13 ` bugzilla-daemon
2014-06-27 8:16 ` bugzilla-daemon
2014-06-27 8:51 ` bugzilla-daemon
2014-06-27 10:20 ` bugzilla-daemon
2014-06-27 16:08 ` bugzilla-daemon
2014-06-27 23:01 ` bugzilla-daemon
2014-06-28 20:21 ` bugzilla-daemon
2014-06-29 7:50 ` bugzilla-daemon
2014-06-30 9:10 ` bugzilla-daemon
2014-06-30 15:59 ` bugzilla-daemon
2014-06-30 16:59 ` bugzilla-daemon
2014-06-30 17:00 ` bugzilla-daemon
2014-06-30 17:45 ` bugzilla-daemon
2014-06-30 18:33 ` bugzilla-daemon
2014-06-30 19:17 ` bugzilla-daemon
2014-06-30 19:19 ` bugzilla-daemon
2014-06-30 19:21 ` bugzilla-daemon
2014-06-30 19:32 ` bugzilla-daemon
2014-06-30 20:37 ` bugzilla-daemon
2014-07-01 17:42 ` bugzilla-daemon
2014-07-02 18:43 ` bugzilla-daemon
2014-07-03 1:07 ` bugzilla-daemon
2014-07-03 19:18 ` bugzilla-daemon
2014-07-05 10:09 ` bugzilla-daemon
2014-07-09 6:58 ` bugzilla-daemon
2014-07-14 19:47 ` bugzilla-daemon
2014-08-03 13:26 ` bugzilla-daemon
2014-10-23 10:08 ` bugzilla-daemon
2014-10-26 17:49 ` bugzilla-daemon
2014-10-26 17:49 ` bugzilla-daemon
2015-02-08 20:42 ` bugzilla-daemon
2015-02-09 17:39 ` bugzilla-daemon
2015-03-27 21:04 ` bugzilla-daemon
2015-03-27 22:33 ` bugzilla-daemon
2015-04-02 0:32 ` bugzilla-daemon
2015-04-15 4:55 ` bugzilla-daemon
2015-05-03 18:18 ` bugzilla-daemon
2015-05-29 16:54 ` bugzilla-daemon
2015-05-30 5:13 ` bugzilla-daemon
2015-06-16 9:08 ` bugzilla-daemon
2015-08-02 12:38 ` bugzilla-daemon
2015-08-02 12:53 ` bugzilla-daemon
2015-08-04 20:46 ` bugzilla-daemon
2015-09-21 14:57 ` bugzilla-daemon
2015-10-03 7:19 ` bugzilla-daemon
2015-10-04 3:26 ` bugzilla-daemon
2015-10-04 11:15 ` bugzilla-daemon
2015-11-01 13:55 ` bugzilla-daemon
2015-11-01 13:58 ` bugzilla-daemon
2015-11-23 3:18 ` bugzilla-daemon
2015-11-23 11:50 ` bugzilla-daemon
2015-11-23 22:13 ` bugzilla-daemon
2015-11-25 18:10 ` bugzilla-daemon
2015-12-18 9:45 ` bugzilla-daemon
2015-12-18 20:38 ` bugzilla-daemon
2015-12-18 23:49 ` bugzilla-daemon
2015-12-18 23:54 ` bugzilla-daemon
2015-12-19 6:36 ` bugzilla-daemon
2015-12-19 14:37 ` bugzilla-daemon
2015-12-19 15:22 ` bugzilla-daemon
2015-12-21 17:12 ` bugzilla-daemon
2015-12-21 22:33 ` bugzilla-daemon
2015-12-21 23:03 ` bugzilla-daemon
2015-12-22 6:29 ` bugzilla-daemon
2015-12-22 8:06 ` bugzilla-daemon
2015-12-22 8:15 ` bugzilla-daemon
2015-12-22 9:25 ` bugzilla-daemon
2015-12-22 9:36 ` bugzilla-daemon
2015-12-22 10:11 ` bugzilla-daemon
2015-12-22 10:27 ` bugzilla-daemon
2015-12-22 10:32 ` bugzilla-daemon
2015-12-22 10:49 ` bugzilla-daemon
2015-12-22 11:00 ` bugzilla-daemon
2015-12-22 12:37 ` bugzilla-daemon
2015-12-22 19:48 ` bugzilla-daemon
2015-12-22 22:38 ` bugzilla-daemon
2015-12-22 22:52 ` bugzilla-daemon
2015-12-23 3:25 ` bugzilla-daemon
2015-12-23 3:48 ` bugzilla-daemon
2015-12-23 13:37 ` bugzilla-daemon
2015-12-23 15:20 ` bugzilla-daemon [this message]
2015-12-29 20:17 ` bugzilla-daemon
2015-12-30 3:48 ` bugzilla-daemon
2015-12-30 22:44 ` bugzilla-daemon
2015-12-31 2:22 ` bugzilla-daemon
2016-01-04 20:00 ` bugzilla-daemon
2016-01-10 10:54 ` bugzilla-daemon
2016-01-10 11:13 ` bugzilla-daemon
2016-01-10 15:33 ` bugzilla-daemon
2016-01-10 16:26 ` bugzilla-daemon
2016-01-10 16:33 ` bugzilla-daemon
2016-01-11 16:31 ` bugzilla-daemon
2016-01-11 18:04 ` bugzilla-daemon
2016-02-05 2:27 ` bugzilla-daemon
2016-02-05 2:29 ` bugzilla-daemon
2016-02-05 8:20 ` bugzilla-daemon
2016-02-05 9:32 ` bugzilla-daemon
2016-02-05 10:30 ` bugzilla-daemon
2016-02-05 13:15 ` bugzilla-daemon
2016-02-05 14:14 ` bugzilla-daemon
2016-02-05 14:21 ` bugzilla-daemon
2016-02-05 14:43 ` bugzilla-daemon
2016-02-05 14:56 ` bugzilla-daemon
2016-02-05 16:29 ` bugzilla-daemon
2016-02-25 12:43 ` bugzilla-daemon
2016-03-02 16:35 ` bugzilla-daemon
2016-03-02 17:17 ` bugzilla-daemon
2016-03-14 12:57 ` bugzilla-daemon
2016-03-17 21:30 ` bugzilla-daemon
2016-03-18 18:35 ` bugzilla-daemon
2016-03-19 20:56 ` bugzilla-daemon
2016-03-22 4:15 ` bugzilla-daemon
2016-03-23 10:47 ` bugzilla-daemon
2016-03-23 17:34 ` bugzilla-daemon
2016-03-23 18:46 ` bugzilla-daemon
2016-03-30 14:40 ` bugzilla-daemon
2016-04-25 9:40 ` bugzilla-daemon
2016-04-28 18:27 ` bugzilla-daemon
2016-04-28 18:28 ` bugzilla-daemon
2016-05-14 11:20 ` bugzilla-daemon
2016-06-06 7:45 ` bugzilla-daemon
2016-06-06 7:51 ` bugzilla-daemon
2016-06-12 18:12 ` bugzilla-daemon
2016-06-13 8:28 ` bugzilla-daemon
2016-07-01 17:07 ` bugzilla-daemon
2016-07-03 20:48 ` bugzilla-daemon
2016-07-04 7:45 ` bugzilla-daemon
2016-07-04 17:57 ` bugzilla-daemon
2016-07-04 19:16 ` bugzilla-daemon
2016-07-04 19:57 ` bugzilla-daemon
2016-07-10 2:07 ` bugzilla-daemon
2016-08-01 11:42 ` bugzilla-daemon
2016-09-04 5:00 ` bugzilla-daemon
2016-09-04 5:03 ` bugzilla-daemon
2016-09-12 22:33 ` bugzilla-daemon
2016-12-08 13:11 ` bugzilla-daemon
2016-12-08 15:44 ` bugzilla-daemon
2016-12-08 22:11 ` bugzilla-daemon
2016-12-09 20:41 ` bugzilla-daemon
2017-01-07 20:38 ` bugzilla-daemon
2017-01-07 20:58 ` bugzilla-daemon
2018-08-31 6:20 ` bugzilla-daemon
2019-03-05 22:44 ` bugzilla-daemon
2019-03-06 9:42 ` bugzilla-daemon
2019-03-06 9:43 ` bugzilla-daemon
2019-03-06 9:56 ` bugzilla-daemon
2019-04-03 11:39 ` bugzilla-daemon
2019-04-03 14:01 ` bugzilla-daemon
2019-04-03 15:34 ` bugzilla-daemon
2019-04-03 16:39 ` bugzilla-daemon
2019-04-03 16:49 ` bugzilla-daemon
2019-09-25 17:51 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-80419-502-x6KBHNdrO9@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).