From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70104] New: radeonsi_compute.c:260:11: error: 'struct pipe_context' has no member named 'bind_compute_sampler_states'
Date: Thu, 03 Oct 2013 22:47:18 +0000 [thread overview]
Message-ID: <bug-70104-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70104
Priority: medium
Bug ID: 70104
Keywords: regression
CC: brianp@vmware.com
Assignee: dri-devel@lists.freedesktop.org
Summary: radeonsi_compute.c:260:11: error: 'struct
pipe_context' has no member named
'bind_compute_sampler_states'
Severity: blocker
Classification: Unclassified
OS: Linux (All)
Reporter: vlee@freedesktop.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
mesa: 800610f9eb6ad24b5fefc9206fb700c7ae2f0ec8 (master)
CC radeonsi_compute.lo
radeonsi_compute.c: In function 'si_init_compute_functions':
radeonsi_compute.c:260:11: error: 'struct pipe_context' has no member named
'bind_compute_sampler_states'
rctx->b.b.bind_compute_sampler_states = si_bind_compute_sampler_states;
^
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-10-03 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 22:47 bugzilla-daemon [this message]
2013-10-03 23:33 ` [Bug 70104] radeonsi_compute.c:260:11: error: 'struct pipe_context' has no member named 'bind_compute_sampler_states' 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-70104-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.