From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71817] New: Git Mesa r600g driver crashes while using llvm
Date: Wed, 20 Nov 2013 01:41:09 +0000 [thread overview]
Message-ID: <bug-71817-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71817
Priority: medium
Bug ID: 71817
Assignee: dri-devel@lists.freedesktop.org
Summary: Git Mesa r600g driver crashes while using llvm
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: sobkas@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 89502
--> https://bugs.freedesktop.org/attachment.cgi?id=89502&action=edit
Gdb output after using glxinfo
R600g crashes while I try to use LLVM support in it.
LLVM: 1:3.4~svn194296-1~exp1
Mesa: e7a5905d8a3960b0981750f8131e3af9acbfcdb8
Error message before segfault:
0x6af6c0: i32 = GlobalAddress<<4 x float> (i32)* @llvm.R600.interp.const> 0
[ORD=1]
Even running glxinfo causes this error.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2462 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
next reply other threads:[~2013-11-20 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 1:41 bugzilla-daemon [this message]
2013-11-20 4:00 ` [Bug 71817] Git Mesa r600g driver crashes while using llvm bugzilla-daemon
2013-11-20 23:00 ` bugzilla-daemon
2013-11-22 14:17 ` bugzilla-daemon
2013-11-22 19:45 ` 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-71817-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.