From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89784] Complex shader compilation fails (spilling related?)
Date: Thu, 26 Mar 2015 23:10:37 +0000 [thread overview]
Message-ID: <bug-89784-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1069 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89784
Bug ID: 89784
Summary: Complex shader compilation fails (spilling related?)
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: greg@chown.ath.cx
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 114655
--> https://bugs.freedesktop.org/attachment.cgi?id=114655&action=edit
LLVM assembly of shader
The attached shader (LLVM assembly, dumped with R600_DEBUG=ps) fails to compile
with latest LLVM trunk. AFAIR it worked at some point with some combination of
Mesa and LLVM, but I couldn't reproduce this.
Compile with
> llc -march=amdgcn -mcpu=SI -mattr=+vgpr-spilling -verify-machineinstrs < bug.ll
to reproduce. It looks like it is spilling related.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2546 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:[~2015-03-26 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 23:10 bugzilla-daemon [this message]
2015-04-25 10:51 ` [Bug 89784] Complex shader compilation fails (spilling related?) 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-89784-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox