From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101572] glMemoryBarrier is backwards Date: Tue, 27 Jun 2017 17:11:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1283789036==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 983066E3D1 for ; Tue, 27 Jun 2017 17:11:44 +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 --===============1283789036== Content-Type: multipart/alternative; boundary="14985835040.8dfB.1379"; charset="UTF-8" --14985835040.8dfB.1379 Date: Tue, 27 Jun 2017 17:11:44 +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=3D101572 --- Comment #4 from Matias N. Goldberg --- After careful thought; I realized I don't need to switch to a dummy FBO; ju= st unset the current one. That DOES make sense to me as while the FBO is bound and I'm executing the compute shader that reads from it, I could as well be telling the driver to= do both things at the same time. I could see why unsetting the FBO would flush the necessary caches (due to OpenGL guarantees, I'm saying "I'm done writing to this FBO" and now reads should be guaranteed to be correct), so I'm going to take this for an answe= r. I don't want to spend much more time on this matter either. Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.= --14985835040.8dfB.1379 Date: Tue, 27 Jun 2017 17:11:44 +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

Commen= t # 4 on bug 10157= 2 from Matias N. Goldberg 
After careful thought; I realized I don't need to switch to a =
dummy FBO; just
unset the current one.

That DOES make sense to me as while the FBO is bound and I'm executing the
compute shader that reads from it, I could as well be telling the driver to=
 do
both things at the same time.

I could see why unsetting the FBO would flush the necessary caches (due to
OpenGL guarantees, I'm saying "I'm done writing to this FBO" and =
now reads
should be guaranteed to be correct), so I'm going to take this for an answe=
r.

I don't want to spend much more time on this matter either.

Thanks.

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