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 55256] New: r600g R600_LLVM=1 bad rendering (light blue instead of grey)
Date: Sun, 23 Sep 2012 20:59:45 +0000	[thread overview]
Message-ID: <bug-55256-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 55256
          Assignee: dri-devel@lists.freedesktop.org
           Summary: r600g R600_LLVM=1 bad rendering (light blue instead of
                    grey)
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: edwin+mesa@etorok.net
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/DRI/R600
           Product: Mesa

Created attachment 67592
  --> https://bugs.freedesktop.org/attachment.cgi?id=67592&action=edit
apitrace

Attached is an apitrace, and screenshots.

Bad behaviour with --enable-r600-llvm-compiler:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 3.0 Mesa 9.1-devel (git-fb40f88)
OpenGL shading language version string: 1.30

If you look at the 'bad.png' screenshot you'll see that the 4th column is light
blue. It should be grey.
With R600_LLVM=0 the good behaviour is seen: good.png.

See the apitrace for the full shader, here is the relevant bit:
    else if (gl_FragCoord.x < 640)
        color = vec4(1.0f, 1.0f, 1.0f, 1.0f);//white
    [...]
        vec4 color0, color1, color2, color3;
        if (gl_FragCoord.y < 200) {
            color0 = color1 = color2 = color;//75%
   [...]
        } else if (xmod < 55 || xmod >= 105 ||
                   ymod < 75 || ymod >= 125) {
            // real color
            // TODO: buggy on r600g with LLVM?
            gl_FragColor = (color0 + color1 + color2 + color3) / 4.0f;

P.S.: the shader is not optimal, most of the branches could be moved out of it,
I haven't tried to minimize the testcase though.

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

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

             reply	other threads:[~2012-09-23 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-23 20:59 bugzilla-daemon [this message]
2012-09-23 21:03 ` [Bug 55256] r600g R600_LLVM=1 bad rendering (light blue instead of grey) bugzilla-daemon
2012-09-23 21:03 ` bugzilla-daemon
2012-09-23 21:04 ` bugzilla-daemon
2012-09-23 21:07 ` bugzilla-daemon
2012-09-23 21:07 ` bugzilla-daemon
2012-09-23 21:07 ` bugzilla-daemon
2012-09-23 21:08 ` bugzilla-daemon
2012-09-23 21:08 ` bugzilla-daemon
2012-09-23 21:12 ` bugzilla-daemon
2012-09-24 10:22 ` bugzilla-daemon
2012-09-24 13:06 ` bugzilla-daemon
2019-09-18 19:00 ` 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-55256-502@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