From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100071] [Regression] Tomb Raider: TressFX broken with recent LLVM
Date: Sun, 05 Mar 2017 21:19:40 +0000 [thread overview]
Message-ID: <bug-100071-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1085 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100071
Bug ID: 100071
Summary: [Regression] Tomb Raider: TressFX broken with recent
LLVM
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: gr.muench@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 130080
--> https://bugs.freedesktop.org/attachment.cgi?id=130080&action=edit
Lara's broken hair...
This weeks LLVM update somehow broke the rendering of TressFX in Tomb Raider.
Radeon HD 7970, Mesa Git
I use precompiled packages from arch repo.
For me last working: lib32-llvm-libs-svn-5.0.0svn_r296294
First time error appeared in: lib32-llvm-libs-svn-5.0.0svn_r296961
No other packages in between, sorry.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2580 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-03-05 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 21:19 bugzilla-daemon [this message]
2017-03-06 1:55 ` [Bug 100071] [Regression] Tomb Raider: TressFX broken with recent LLVM bugzilla-daemon
2017-03-07 22:19 ` bugzilla-daemon
2017-03-19 15:54 ` 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-100071-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.