[email protected] writes: > From: Tom Stellard <[email protected]> > > This structure is used to pass non-TGSI programs to the drivers. clover > will use this for LLVM bytecode programs. > --- > src/gallium/include/pipe/p_state.h | 9 +++++++++ > 1 files changed, 9 insertions(+), 0 deletions(-) > > diff --git a/src/gallium/include/pipe/p_state.h > b/src/gallium/include/pipe/p_state.h > index 51a956d..fb4a286 100644 > --- a/src/gallium/include/pipe/p_state.h > +++ b/src/gallium/include/pipe/p_state.h > @@ -593,6 +593,15 @@ struct pipe_resolve_info > unsigned mask; /**< PIPE_MASK_RGBA, Z, S or ZS */ > }; > > +/** > + * Structure for passing non-TGSI compute programs to the drivers. > + */ > +struct pipe_compute_program > +{ > + uint32_t num_bytes; /**< Number of bytes pointed to by prog. */ > + unsigned char * prog; /**< The compute program. */ > +}; > +
The name of the struct seems misleading to me, I think this is only ever
going to be useful for LLVM programs... How about 'pipe_llvm_program'
or 'pipe_llvm_program_header'?
> struct pipe_compute_state
> {
> const void *prog; /**< Compute program to be executed. */
pgpKrqxSTjlWT.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
