From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58666] New: rv670 + llvm = errors.
Date: Sat, 22 Dec 2012 23:46:55 +0000 [thread overview]
Message-ID: <bug-58666-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 932 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58666
Priority: medium
Bug ID: 58666
Assignee: dri-devel@lists.freedesktop.org
Summary: rv670 + llvm = errors.
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: lists@andyfurniss.entadsl.com
Hardware: x86 (IA32)
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
I've only just tested this AGP HD3850 card with tstellar LLVM (or any llvm) as
it's been out of the PC since Feb.
Both last week and now with updated llvm/mesa gits, running anything eg. gears
will just flood -
EE r600_asm.c:122 r600_bytecode_get_num_operands - Need instruction operand
number for 0xc.
Works OK with R600_LLVM=0
This was tested with drm-fixes kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2210 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:[~2012-12-22 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 23:46 bugzilla-daemon [this message]
2012-12-23 10:41 ` [Bug 58666] rv670 + llvm = errors bugzilla-daemon
2013-02-01 14:08 ` bugzilla-daemon
2013-02-01 15:06 ` bugzilla-daemon
2013-02-01 15:46 ` bugzilla-daemon
2013-02-01 16:01 ` bugzilla-daemon
2013-02-01 17:41 ` bugzilla-daemon
2013-02-01 22:47 ` 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-58666-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.