mesa/src/gallium
Eric Anholt 38c6c0f5b4 vc4: Add a helper for making driver-specific NIR load_uniform for GL state
In order to move more of our lowering into NIR, we need the ability to
reference various pipeline state (like texture rectangle scaling factors
or blend colors), so we just set those up as a load_uniform with a big
offset to indicate that it's not within the shader's uniform storage and
is one of our state values.
2015-08-14 11:39:18 -07:00
..
auxiliary winsys/amdgpu: add a new winsys for the new kernel driver 2015-08-14 15:02:28 +02:00
docs gallium: add an interface for EXT_depth_bounds_test 2015-08-14 15:01:51 +02:00
drivers vc4: Add a helper for making driver-specific NIR load_uniform for GL state 2015-08-14 11:39:18 -07:00
include vl: add HEVC profiles and defines 2015-08-14 15:02:28 +02:00
state_trackers st/vdpau: add HEVC support v2 2015-08-14 15:02:28 +02:00
targets winsys/amdgpu: add a new winsys for the new kernel driver 2015-08-14 15:02:28 +02:00
tests gallium/tests: use cso_set_samplers 2015-07-23 00:59:23 +02:00
tools gallium: add an index argument to create_query 2014-07-01 11:34:31 -04:00
winsys radeon/vce: disable VCE dual instance for harvest part 2015-08-14 15:02:31 +02:00
Android.common.mk android: enable the radeonsi driver 2015-06-09 12:25:50 -07:00
Android.mk winsys/amdgpu: add a new winsys for the new kernel driver 2015-08-14 15:02:28 +02:00
Automake.inc pipe-loader: remove pipe_loader_sw_probe_xlib 2015-07-13 19:57:38 +01:00
Makefile.am winsys/amdgpu: add a new winsys for the new kernel driver 2015-08-14 15:02:28 +02:00
README.portability gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
SConscript scons: don't build the kms-dri winsys 2015-07-22 16:35:25 +01:00

	      CROSS-PLATFORM PORTABILITY GUIDELINES FOR GALLIUM3D 


= General Considerations =

The state tracker and winsys driver support a rather limited number of
platforms. However, the pipe drivers are meant to run in a wide number of
platforms. Hence the pipe drivers, the auxiliary modules, and all public
headers in general, should strictly follow these guidelines to ensure


= Compiler Support =

* Include the p_compiler.h.

* Cast explicitly when converting to integer types of smaller sizes.

* Cast explicitly when converting between float, double and integral types.

* Don't use named struct initializers.

* Don't use variable number of macro arguments. Use static inline functions
instead.

* Don't use C99 features.

= Standard Library =

* Avoid including standard library headers. Most standard library functions are
not available in Windows Kernel Mode. Use the appropriate p_*.h include.

== Memory Allocation ==

* Use MALLOC, CALLOC, FREE instead of the malloc, calloc, free functions.

* Use align_pointer() function defined in u_memory.h for aligning pointers
 in a portable way.

== Debugging ==

* Use the functions/macros in p_debug.h.

* Don't include assert.h, call abort, printf, etc.


= Code Style =

== Inherantice in C ==

The main thing we do is mimic inheritance by structure containment.

Here's a silly made-up example:

/* base class */
struct buffer
{
  int size;
  void (*validate)(struct buffer *buf);
};

/* sub-class of bufffer */
struct texture_buffer
{
  struct buffer base;  /* the base class, MUST COME FIRST! */
  int format;
  int width, height;
};


Then, we'll typically have cast-wrapper functions to convert base-class 
pointers to sub-class pointers where needed:

static inline struct vertex_buffer *vertex_buffer(struct buffer *buf)
{
  return (struct vertex_buffer *) buf;
}


To create/init a sub-classed object:

struct buffer *create_texture_buffer(int w, int h, int format)
{
  struct texture_buffer *t = malloc(sizeof(*t));
  t->format = format;
  t->width = w;
  t->height = h;
  t->base.size = w * h;
  t->base.validate = tex_validate;
  return &t->base;
}

Example sub-class method:

void tex_validate(struct buffer *buf)
{
  struct texture_buffer *tb = texture_buffer(buf);
  assert(tb->format);
  assert(tb->width);
  assert(tb->height);
}


Note that we typically do not use typedefs to make "class names"; we use
'struct whatever' everywhere.

Gallium's pipe_context and the subclassed psb_context, etc are prime examples 
of this.  There's also many examples in Mesa and the Mesa state tracker.