From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101572] glMemoryBarrier is backwards
Date: Tue, 27 Jun 2017 09:12:10 +0000 [thread overview]
Message-ID: <bug-101572-502-D5XdtFTs03@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101572-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 954 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101572
Nicolai Hähnle <nhaehnle@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #1 from Nicolai Hähnle <nhaehnle@gmail.com> ---
You're misinterpreting the spec.
glMemoryBarrier ensures that **writes from shaders** are visible to whatever
consumer you indicate with the given flag bits.
What you seem to be trying to do is ensure that **writes via the framebuffer**
are visible in subsequent compute shader invocations. For that, you need to
either:
(1) Bind a different framebuffer, or (probably more appropriate to what you're
trying to do)
(2) use glTextureBarrier.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2407 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:[~2017-06-27 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 4:54 [Bug 101572] glMemoryBarrier is backwards bugzilla-daemon
2017-06-27 9:12 ` bugzilla-daemon [this message]
2017-06-27 16:46 ` bugzilla-daemon
2017-06-27 16:49 ` bugzilla-daemon
2017-06-27 17:11 ` bugzilla-daemon
2017-06-27 17:12 ` 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-101572-502-D5XdtFTs03@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;
as well as URLs for NNTP newsgroup(s).