All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65190] New: glxgears on r600g (rv770) is garbled with llvm enabled
Date: Thu, 30 May 2013 20:30:24 +0000	[thread overview]
Message-ID: <bug-65190-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 65190
          Assignee: dri-devel@lists.freedesktop.org
           Summary: glxgears on r600g (rv770) is garbled with llvm enabled
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: ace@sannes.org
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 80067
  --> https://bugs.freedesktop.org/attachment.cgi?id=80067&action=edit
output of R600-DEBUG=vs,ps glxgears

Running glxgears gives garbled output, tstellar on irc asked me to file a bug
with the output of R600_DEBUG=vs,ps glxgears

I have a rv770 card (4870) and have compiled mesa with llvm.

It does not get garbled if I run with:

R600_DEBUG=sb works.

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

[-- Attachment #1.2: Type: text/html, Size: 2427 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:[~2013-05-30 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 20:30 bugzilla-daemon [this message]
2013-05-30 20:44 ` [Bug 65190] glxgears on r600g (rv770) is garbled with llvm enabled bugzilla-daemon
2013-06-01  9:08 ` bugzilla-daemon
2015-04-21 17:44 ` 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-65190-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.