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 65438] GTK apps crash X11 since last update of LLVMM
Date: Sat, 08 Jun 2013 13:01:45 +0000	[thread overview]
Message-ID: <bug-65438-502-NakbIIBhg2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-65438-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from hadack@gmx.de ---
I have the same problem on a 7750 CAPE VERDE card.

When starting a xfce session X craches with the error message from above,
starting kde works fine.

bisecting shows this bad commit:

8a72c73032707c7b3c042b716286a1ac33720991 is the first bad commit
commit 8a72c73032707c7b3c042b716286a1ac33720991
Author: Tom Stellard <thomas.stellard@amd.com>
Date:   Mon Jun 3 17:39:46 2013 +0000

    R600/SI: Fixup CopyToReg register class in PostprocessISelDAG()

    The CopyToReg nodes will sometimes try to copy a value from a VGPR to an
    SGPR.  This kind of copy is not possible, so we need to detect
    VGPR->SGPR copies and do something else.  The current strategy is to
    replace these copies with VGPR->VGPR copies and hope that all the users
    of CopyToReg can accept VGPRs as arguments.

    git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@183132
91177308-0d34-0410-b5e6-96231b3b80d8

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

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

  parent reply	other threads:[~2013-06-08 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  1:51 [Bug 65438] New: GTK apps crash X11 since last update of LLVMM bugzilla-daemon
2013-06-06  1:51 ` [Bug 65438] " bugzilla-daemon
2013-06-06 10:03 ` bugzilla-daemon
2013-06-06 15:13 ` bugzilla-daemon
2013-06-07 10:21 ` bugzilla-daemon
2013-06-08 13:01 ` bugzilla-daemon [this message]
2013-06-08 23:49 ` bugzilla-daemon
2013-06-08 23:52 ` bugzilla-daemon
2013-06-09  0:12 ` bugzilla-daemon
2013-06-09 14:53 ` bugzilla-daemon
2013-06-10 16:42 ` bugzilla-daemon
2013-06-10 20:19 ` bugzilla-daemon
2013-06-10 22:13 ` bugzilla-daemon
2013-06-14  8:28 ` bugzilla-daemon
2013-06-14 18:55 ` 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-65438-502-NakbIIBhg2@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).