From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 99013] [regression, bisected] radeonsi: commit 4c8c13b3 "Use amdgcn intrinsics for fs interpolation" makes system unusable Date: Thu, 08 Dec 2016 01:55:57 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1045474852==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id CEC296E63C for ; Thu, 8 Dec 2016 01:55:57 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1045474852== Content-Type: multipart/alternative; boundary="14811621572.c51Ba7F.26212"; charset="UTF-8" --14811621572.c51Ba7F.26212 Date: Thu, 8 Dec 2016 01:55:57 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D99013 --- Comment #5 from Michel D=C3=A4nzer --- (In reply to Christoph Haag from comment #4) > 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 co= de > that's not used for any of the actual llvm releases. It's not about what we want =E2=80=94 there's simply no way to know which S= VN 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 tr= y to ensure is that current Mesa Git master works with current LLVM SVN trunk. > 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. Fixed in https://cgit.freedesktop.org/mesa/mesa/commit/?id=3D26ba8c920d2727cae8ab450= 96db70e4691b00245 . --=20 You are receiving this mail because: You are the assignee for the bug.= --14811621572.c51Ba7F.26212 Date: Thu, 8 Dec 2016 01:55:57 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 5 on bug 99013<= /a> from Michel D=C3=A4nzer 
(In reply to Christoph Haag from comment #4)
> Which makes bisecting a lot harder, but understa=
ndable 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.

It's not about what we want =E2=80=94 there's simply no way to know which S=
VN 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 tr=
y to
ensure is that current Mesa Git master works with current LLVM SVN trunk.


> 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.

Fixed in
https://cgit.freedesktop.org/mesa/mesa/commit=
/?id=3D26ba8c920d2727cae8ab45096db70e4691b00245
.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14811621572.c51Ba7F.26212-- --===============1045474852== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1045474852==--