mesa/src/gallium
Marek Olšák 26222932c0 gallium: add PIPE_CAP_MAX_SHADER_PATCH_VARYINGS
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
2015-07-16 16:09:20 +02:00
..
auxiliary auxiliary/vl: use the correct screen index 2015-07-13 20:43:11 +01:00
docs gallium: add PIPE_CAP_MAX_SHADER_PATCH_VARYINGS 2015-07-16 16:09:20 +02:00
drivers gallium: add PIPE_CAP_MAX_SHADER_PATCH_VARYINGS 2015-07-16 16:09:20 +02:00
include gallium: add PIPE_CAP_MAX_SHADER_PATCH_VARYINGS 2015-07-16 16:09:20 +02:00
state_trackers clover: little OpenCL status code logging clean 2015-07-16 13:48:20 +03:00
targets automake: remove empty GALLIUM_PIPE_LOADER_LIBS 2015-07-13 19:57:34 +01:00
tests automake: remove empty GALLIUM_PIPE_LOADER_LIBS 2015-07-13 19:57:34 +01:00
tools gallium: add an index argument to create_query 2014-07-01 11:34:31 -04:00
winsys winsys/radeon: use os_wait_until_zero in radeon_bo_set_tiling 2015-07-05 15:08:59 +02:00
Android.common.mk android: enable the radeonsi driver 2015-06-09 12:25:50 -07:00
Android.mk vc4: Add support for building on Android. 2015-06-15 10:32:23 -07:00
Automake.inc pipe-loader: remove pipe_loader_sw_probe_xlib 2015-07-13 19:57:38 +01:00
Makefile.am galahad: remove driver 2015-03-21 17:18:28 +00:00
README.portability
SConscript scons: add target osmesa using gallium state tracker. 2015-04-27 15:18:36 +01:00

README.portability

	      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.

* Don't use the 'inline' keyword, use the INLINE macro in p_compiler.h instead.

* 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.