From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94008] Grow Home colors are wrong with HD6950
Date: Tue, 16 Feb 2016 10:46:25 +0000 [thread overview]
Message-ID: <bug-94008-502-tzgXp2P3T2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94008-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1777 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94008
Alejandro Piñeiro (freenode IRC: apinheiro) <apinheiro@igalia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |apinheiro@igalia.com
--- Comment #1 from Alejandro Piñeiro (freenode IRC: apinheiro) <apinheiro@igalia.com> ---
(In reply to serge from comment #0)
> I also made an apitrace which you can find on the following link, if someone
> is interested into looking at this issue:
>
> https://drive.google.com/file/d/0B6bdV-rKtJnFWDlvWE1vZnFtaXc/view?usp=sharing
Under the risk of adding noise here, I tried this apitrace on a intel HD4600
(haswell). I got several visual artifacts (in addition to be really slow),
getting several performance related debug warnings. For example, at the initial
phase, where it is mostly compiling shaders:
10202: message: shader compiler performance issue 478: SIMD16 shader failed to
compile: FS compile failed: Failure to register allocate. Reduce number of
live scalar values to avoid this
And then, when running the log and the menu, messages like the following:
327430: message: api performance issue 1506: Scanning index buffer to compute
index buffer bounds. Use glDrawRangeElements() to avoid this
3836043: message: api performance issue 1553: GTT mapping a busy miptree BO
stalled and took 1516.024 ms
Anyway, probably this would need to be taken with a grain of salt, as usually
games detect hw capabilities in order to know what to use. Probably it would be
worth to try the game on a intel hw (unfourtunately I don't have access to that
game).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3277 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-16 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 13:23 [Bug 94008] Grow Home colors are wrong with HD6950 bugzilla-daemon
2016-02-16 10:46 ` bugzilla-daemon [this message]
2016-02-16 17:49 ` bugzilla-daemon
2019-09-18 19:21 ` 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-94008-502-tzgXp2P3T2@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