mesa/src/gallium
Ilia Mirkin edd494ddf0 nv50/ir: make sure to fetch all sources before creating instruction
We must fetch all sources into the instruction stream before generating
the instruction that uses them. Otherwise we'll define values after
using them, which won't work so well.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Tested-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
2016-02-03 18:40:38 -05:00
..
auxiliary vl: add zig zag scan for list 4x4 2016-02-02 20:29:43 -05:00
docs gallium: fix the documentation of PIPE_CAP_MAX_TEXTURE_BUFFER_SIZE 2016-02-03 14:12:37 +01:00
drivers nv50/ir: make sure to fetch all sources before creating instruction 2016-02-03 18:40:38 -05:00
include gallium: Add PIPE_CAP_SURFACE_REINTERPRET_BLOCKS 2016-02-03 14:10:34 +01:00
state_trackers st/omx/dec/h264: fix corruption when scaling matrix present flag set 2016-02-02 20:29:47 -05:00
targets virgl: also build vtest for Android 2016-02-02 09:58:51 +10:00
tests gallium/tests: fix build with clang compiler 2016-01-03 12:18:00 +01:00
tools gallium: add an index argument to create_query 2014-07-01 11:34:31 -04:00
winsys winsys/radeon: Do not deinit the pb cache if it was not initialized 2016-02-02 21:11:15 +01:00
Android.common.mk android: enable the radeonsi driver 2015-06-09 12:25:50 -07:00
Android.mk virgl: also build vtest for Android 2016-02-02 09:58:51 +10: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.