dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101596] Blender renders black UI elements
Date: Wed, 05 Jul 2017 03:41:18 +0000	[thread overview]
Message-ID: <bug-101596-502-x0LApTKNoV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101596-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1076 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101596

--- Comment #7 from Matias N. Goldberg <dark_sylinc@yahoo.com.ar> ---
As I keep reading the code and getting familiar, everything starts making
sense:

/**
* If a shader can be created when we get its source.
* This means it has only 1 variant, not counting glBitmap and
* glDrawPixels.
*/
boolean shader_has_one_variant[MESA_SHADER_STAGES];

The problem is that after glDrawPixels creates its own variant; st_update_fp
will end up using glDrawPixels' variant, instead of the non-glDrawPixels one.

The same problem happens if glBitmap is used.

One simple solution would be to add the variant to the end of the linked list,
but this may affect the performance profile of radeonsi (i.e. assuming
variations created last are more likely to be used than variations created
first).
The performance concerns can be negated by adding the variation to the end of
the linked list ONLY if glDrawPixels or glBitmap is the caller.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1838 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

  parent reply	other threads:[~2017-07-05  3:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 12:18 [Bug 101596] Blender renders black UI elements bugzilla-daemon
2017-06-26 12:19 ` bugzilla-daemon
2017-06-26 12:19 ` bugzilla-daemon
2017-06-26 12:21 ` bugzilla-daemon
2017-06-26 22:38 ` bugzilla-daemon
2017-07-05  3:22 ` bugzilla-daemon
2017-07-05  3:33 ` bugzilla-daemon
2017-07-05  3:36 ` bugzilla-daemon
2017-07-05  3:41 ` bugzilla-daemon [this message]
2017-07-05 17:05 ` bugzilla-daemon
2017-07-05 17:53 ` bugzilla-daemon
2017-07-06  0:59 ` bugzilla-daemon
2017-07-07 23:52 ` bugzilla-daemon
2017-07-08  2:41 ` 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-101596-502-x0LApTKNoV@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).