From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99013] [regression, bisected] radeonsi: commit 4c8c13b3 "Use amdgcn intrinsics for fs interpolation" makes system unusable
Date: Wed, 07 Dec 2016 20:53:16 +0000 [thread overview]
Message-ID: <bug-99013-502-dwsE3OjXP7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99013-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99013
--- Comment #4 from Christoph Haag <haagch@frickel.club> ---
Which makes bisecting a lot harder, but understandable that the devs don't want
to have the burden of having many intermediate workarounds in the code that's
not used for any of the actual llvm releases.
But what I came here to say is that I have llvm 3.9.0 from the Archlinux Repos
and this commit breaks everything for me too.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1521 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 prev parent reply other threads:[~2016-12-07 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 4:59 [Bug 99013] [regression, bisected] radeonsi: commit 4c8c13b3 "Use amdgcn intrinsics for fs interpolation" makes system unusable bugzilla-daemon
2016-12-07 6:32 ` bugzilla-daemon
2016-12-07 18:09 ` bugzilla-daemon
2016-12-07 20:21 ` bugzilla-daemon
2016-12-07 20:53 ` bugzilla-daemon [this message]
2016-12-08 1:55 ` bugzilla-daemon
2016-12-08 7:37 ` bugzilla-daemon
2016-12-08 7:41 ` bugzilla-daemon
2016-12-08 11:17 ` bugzilla-daemon
2016-12-08 17:36 ` bugzilla-daemon
2016-12-08 21:30 ` bugzilla-daemon
2016-12-09 2:19 ` 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-99013-502-dwsE3OjXP7@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