mesa/src/gallium
José Fonseca 5aaa4bafe0 gallivm: Add and use lp_build_lerp_3d.
Reviewed-by: Roland Scheidegger <sroland@vmware.com>
2013-05-17 20:22:50 +01:00
..
auxiliary gallivm: Add and use lp_build_lerp_3d. 2013-05-17 20:22:50 +01:00
docs gallium: add PIPE_CAP_MAX_TEXTURE_BUFFER_SIZE for GL 2013-05-11 23:45:01 +02:00
drivers radeon/llvm: Run standard optimization passes on conpute shader modules 2013-05-17 07:38:01 -07:00
include gallium: add PIPE_CAP_MAX_TEXTURE_BUFFER_SIZE for GL 2013-05-11 23:45:01 +02:00
state_trackers vl/vdpau: fix PresentationQueueQuerySurfaceStatus 2013-05-14 15:16:15 +02:00
targets targets/dri-i915: Force c++ linker in all cases 2013-05-09 17:04:27 -07:00
tests graw/tgsi_dump: Fix gdb macro. 2013-05-14 15:36:37 +01:00
tools trace: measure time for each gallium call 2013-02-01 08:00:28 -07:00
winsys winsys/intel: test for and expose address swizzling 2013-05-16 11:24:59 +08:00
Android.common.mk
Android.mk android: add ilo to the build system 2013-05-06 07:20:07 -07:00
Automake.inc Remove MESA_PIC_FLAGS macro 2013-01-10 22:01:31 +01:00
README.portability
SConscript scons: remove nouveau build 2013-05-03 18:44:57 +02: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.