From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67046] [radeonsi] pixmark_piano benchmark from geeks3D gputest fail with a llvm error output
Date: Fri, 19 Jul 2013 10:32:27 +0000 [thread overview]
Message-ID: <bug-67046-502-xUn0ZTryZo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67046-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 957 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67046
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
|.org |org
Component|Drivers/Gallium/radeonsi |Mesa core
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
AFAICT the real problem is this, visible with a debugging build of Mesa:
../../../../src/gallium/auxiliary/gallivm/lp_bld_tgsi_soa.c:2190:lp_emit_declaration_soa:
Assertion `idx < 256' failed.
This can be avoided by bumping LP_MAX_TGSI_TEMPS, but it looks like the app
and/or glsl-to-tgsi aren't paying attention to the maximum number of
temporaries advertised by the driver.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2513 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
prev parent reply other threads:[~2013-07-19 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 13:56 [Bug 67046] New: [radeonsi] pixmark_piano benchmark from geeks3D gputest fail with a llvm error output bugzilla-daemon
2013-07-19 10:32 ` bugzilla-daemon [this message]
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-67046-502-xUn0ZTryZo@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