<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [regression, bisected] radeonsi: commit 4c8c13b3 "Use amdgcn intrinsics for fs interpolation" makes system unusable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99013#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [regression, bisected] radeonsi: commit 4c8c13b3 "Use amdgcn intrinsics for fs interpolation" makes system unusable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99013">bug 99013</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Christoph Haag from <a href="show_bug.cgi?id=99013#c4">comment #4</a>)
<span class="quote">> 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.</span >
It's not about what we want — there's simply no way to know which SVN revision
of LLVM we're building against. So it's not possible for Mesa to work with LLVM
SVN snapshots both before and after incompatible API changes. All we can try to
ensure is that current Mesa Git master works with current LLVM SVN trunk.
<span class="quote">> 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.</span >
Fixed in
<a href="https://cgit.freedesktop.org/mesa/mesa/commit/?id=26ba8c920d2727cae8ab45096db70e4691b00245">https://cgit.freedesktop.org/mesa/mesa/commit/?id=26ba8c920d2727cae8ab45096db70e4691b00245</a>
.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>