All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 54230] New: r600-llvm-compiler completely broken at CAYMAN
Date: Wed, 29 Aug 2012 20:48:36 +0000	[thread overview]
Message-ID: <bug-54230-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 54230
           Summary: r600-llvm-compiler completely broken at CAYMAN
    Classification: Unclassified
           Product: DRI
           Version: XOrg CVS
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: v10lator@myway.de


Created attachment 66294
  --> https://bugs.freedesktop.org/attachment.cgi?id=66294
The desktop with compiz.

Today I decided to give the llvm shader compiler a try, so I compiled mesa
(from git) with it enabled.
The result was a completely broken desktop. With the help of a 2d desktop
environment I was able to capture some screenshots/videos from Minecraft (see
attachments).

No information in dmesg and/or Xorg.0.log (I attach them anyway).

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

             reply	other threads:[~2012-08-29 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 20:48 bugzilla-daemon [this message]
2012-08-29 20:49 ` [Bug 54230] r600-llvm-compiler completely broken at CAYMAN bugzilla-daemon
2012-08-29 20:54 ` bugzilla-daemon
2012-08-29 20:55 ` bugzilla-daemon
2012-08-30  8:54 ` bugzilla-daemon
2012-08-30 13:11 ` bugzilla-daemon
2012-08-30 13:13 ` bugzilla-daemon
2012-08-31 12:37 ` bugzilla-daemon
2012-08-31 12:38 ` bugzilla-daemon
2012-08-31 16:22 ` 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-54230-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.