mesa/src/gallium
Dave Airlie 3d942ee4e5 r600/shader: add utility functions to do single slot arithmatic
These utilities are to be used to do things like integer adds and
multiplies to be used in calculating the LDS offsets etc.

It handles CAYMAN MULLO differences as well.

Signed-off-by: Dave Airlie <airlied@redhat.com>
(cherry picked from commit 0696ebc899)
2015-12-12 19:39:03 +00:00
..
auxiliary vl/buffers: fixes vl_video_buffer_formats for RGBX 2015-12-04 16:33:10 +00:00
docs gallium: add support for gl_HelperInvocation semantic 2015-11-12 17:58:23 -05:00
drivers r600/shader: add utility functions to do single slot arithmatic 2015-12-12 19:39:03 +00:00
include target-helpers: remove inline_drm_helper.h 2015-11-21 12:52:20 +00:00
state_trackers st/va: disable MPEG4 by default v2 2015-12-12 19:39:01 +00:00
targets automake: fix some occurrences of hardcoded -ldl and -lpthread 2015-12-04 16:36:44 +00:00
tests gallium: rename libpipe_loader to libpipe_loader_dynamic 2015-11-21 12:52:19 +00:00
tools gallium: add an index argument to create_query 2014-07-01 11:34:31 -04:00
winsys winsys/radeon: Use CPU page size instead of hardcoding 4096 bytes v3 2015-11-09 17:24:32 +09:00
Android.common.mk android: enable the radeonsi driver 2015-06-09 12:25:50 -07:00
Android.mk pipe-loader: add preliminary Android support 2015-11-21 12:52:20 +00:00
Automake.inc gallium: keep the libdrm link alongside libkmsdri.la 2015-11-21 12:52:18 +00:00
Makefile.am automake: remove no longer needed HAVE_LOADER_GALLIUM conditional 2015-11-21 12:52:19 +00:00
README.portability gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
SConscript pipe-loader: add preliminary scons support 2015-11-21 12:52:20 +00: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.