On 09/13/2012 02:41 PM, Tom Stellard wrote:
From: Tom Stellard<thomas.stell...@amd.com>
pipe_compute_state::prog may contain multiple kernels, but only one will
be relevant for each pipe_compute_state object. The entry_symbol member
is used to specify which kernel should be executed with this
pipe_compute_state.
---
src/gallium/include/pipe/p_state.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/gallium/include/pipe/p_state.h
b/src/gallium/include/pipe/p_state.h
index 9ea9c0e..e18e0af 100644
--- a/src/gallium/include/pipe/p_state.h
+++ b/src/gallium/include/pipe/p_state.h
@@ -602,6 +602,10 @@ struct pipe_llvm_program_header
struct pipe_compute_state
{
const void *prog; /**< Compute program to be executed. */
+ const char *entry_symbol; /** < Name of the symbol that contains the
+ code to execute. (i.e. for code that
+ contains multiple kernels, this will the
+ name of the kernel to be executed).> */
Minor nit: the doxygen comment should start with "/**<" (no space) and
the '>' at the end of the comment isn't needed.
unsigned req_local_mem; /**< Required size of the LOCAL resource. */
unsigned req_private_mem; /**< Required size of the PRIVATE resource. */
unsigned req_input_mem; /**< Required size of the INPUT resource. */
-Brian
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
