From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90056] Unigine Valley regression since radeon/llvm: Run LLVM's instruction combining pass
Date: Thu, 16 Apr 2015 21:45:51 +0000 [thread overview]
Message-ID: <bug-90056-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1361 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90056
Bug ID: 90056
Summary: Unigine Valley regression since radeon/llvm: Run
LLVM's instruction combining pass
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: adf.lists@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
R9270X
Since
commit c6d79ed289a75f13c65f011be870f7e43a0fedc7
Author: Tom Stellard <thomas.stellard@amd.com>
Date: Fri Apr 10 17:07:16 2015 +0000
radeon/llvm: Run LLVM's instruction combining pass
This should improve code quality in general and will help with some
future changes to how we emit kill instructions.
shader-db shows a few regressions, but these don't seem to be the result
of deficiencies in instcombine. They're mostly caused by the scheduler
making different decisions than before.
Unigine Valley quits saying -
Unhandled loop condition!
UNREACHABLE executed at SIAnnotateControlFlow.cpp:267!
Only tried my normal settings on valley which are
quality ultra + 8x AA
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2734 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-04-16 21:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 21:45 bugzilla-daemon [this message]
2015-04-16 23:16 ` [Bug 90056] Unigine Valley regression since radeon/llvm: Run LLVM's instruction combining pass bugzilla-daemon
2015-04-16 23:41 ` bugzilla-daemon
2015-04-17 7:22 ` bugzilla-daemon
2015-04-25 22:53 ` bugzilla-daemon
2015-04-28 8:22 ` bugzilla-daemon
2015-04-28 10:54 ` bugzilla-daemon
2015-04-28 13:03 ` bugzilla-daemon
2015-04-28 17:03 ` bugzilla-daemon
2015-04-28 17:25 ` bugzilla-daemon
2015-04-28 18:03 ` bugzilla-daemon
2015-04-29 2:04 ` bugzilla-daemon
2015-04-29 2:06 ` bugzilla-daemon
2015-04-29 9:48 ` bugzilla-daemon
2015-04-29 21:02 ` bugzilla-daemon
2015-04-30 21:19 ` bugzilla-daemon
2015-04-30 22:17 ` bugzilla-daemon
2015-05-01 3:57 ` bugzilla-daemon
2015-05-11 21:38 ` bugzilla-daemon
2015-05-25 22:06 ` 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-90056-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.