dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42435] Suspected loss of varyings between shaders
Date: Tue, 01 Nov 2011 22:27:29 +0000	[thread overview]
Message-ID: <bug-42435-502-4T4aCaPoTu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42435-502@http.bugs.freedesktop.org/>

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

--- Comment #4 from Alexander Sabourenkov <screwdriver@lxnt.info> 2011-11-01 15:27:29 PDT ---
The workaround did not help r600g. Same black screen. In addition, the non-llvm
swrast draws point sprites 60 pixels in size instead of requested 16 (my
original shaders get texture sub-image size via varyings too), plus it draws
solid-black-textured point sprites as single pixels. r600c (as of Oct 27 git,
just before being axed) works though.

Not knowing whether any given black screen is a bug, or legitimate undefined
behaviour that just happens to work on some other renderer is driving me mad.

I managed to cut down the test case to bare minimum.

Usage:

./testbed <shaderset> <mesadriver>

shaderset is either "working" or "failing" - loads similarly named shaders.

"working" shader set does texture sampling in fragment shader
"failing" shader set does texture sampling in vertex shader and passes
the color as a varying vec4.

mesadriver is:
hw - default, LIBGL_ALWAYS_SOFTWARE and LIBGL_DRIVERS_PATH unset.
hw-alt - use .so from dri-alternates (x64-86 hardcoded, sorry).
sw - LIBGL_ALWAYS_SOFTWARE=y
sw-alt - as above, but use .so from dri-alternates.

For the Oct 27 git these map to r600g, r600c, swrast, llvmpipe on my box.

Of those:

"failing" llvmpipe - works as intended, vertical colored bars (composed of
16x16 point sprites), one sprite is dark green - left unpainted intentionally.
"working" llvmpipe - same (ok)
"failing" DRI - ok
"working" DRI - ok
"failing" r600g - all sprites black 
"working" r600g - all sprites black 
"failing" old-swrast  - single pixels instead of 16x16, but looks like color is
right
"working" old-swrast  - same as "failing"

The hardware is rv770 9440.

I'd say there's a problem with r600g and a different one with old swrast.

There's also intermittent display corruption mainly on areas in xterm redrawn
(but not those that get scrolled up) immediately after launching the testcase.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-11-01 22:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 14:40 [Bug 42435] New: Suspected loss of varyings between shaders bugzilla-daemon
2011-10-31 14:43 ` [Bug 42435] " bugzilla-daemon
2011-10-31 14:50 ` bugzilla-daemon
2011-11-01  9:42 ` bugzilla-daemon
2011-11-01 22:27 ` bugzilla-daemon [this message]
2011-11-01 22:28 ` bugzilla-daemon
2011-11-02  0:31 ` bugzilla-daemon
2011-11-02  0:53 ` bugzilla-daemon
2011-11-02  0:54 ` bugzilla-daemon
2011-11-02  1:03 ` bugzilla-daemon
2011-11-02  1:40 ` bugzilla-daemon
2011-11-02  1:41 ` bugzilla-daemon
2011-11-02  4:56 ` bugzilla-daemon
2011-11-02  7:41 ` bugzilla-daemon
2012-02-25 22:26 ` bugzilla-daemon
2012-02-26 15:29 ` 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-42435-502-4T4aCaPoTu@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