From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts
Date: Mon, 27 May 2019 18:47:35 +0000 [thread overview]
Message-ID: <bug-106302-502-kWdfAca3Mp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106302-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 769 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106302
--- Comment #3 from Pierre-Eric Pelloux-Prayer <pierre-eric@damsy.net> ---
I agree but "D.3.1 Determining Completion of Changes to an object" says: "The
contents of an object T are considered to have been changed once a command such
as described in section D.3 has completed. Completion of a command may be
determined either by calling Finish, or by calling FenceSync and executing a
WaitSync command on the associated sync object.".
So in my understanding, the contents of your texture in your example haven't
changed by the end of createTexture() (because the glTexImage command hasn't
completed) so rule 4 isn't relevant.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1656 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-27 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 20:06 [Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts bugzilla-daemon
2019-05-22 11:59 ` bugzilla-daemon
2019-05-25 20:07 ` bugzilla-daemon
2019-05-27 18:47 ` bugzilla-daemon [this message]
2019-05-28 18:59 ` bugzilla-daemon
2019-05-29 8:00 ` 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-106302-502-kWdfAca3Mp@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).