mesa/src/gallium
José Fonseca 01b39b053b r600g: Swap the util_blitter_destroy call order.
Trivial change that avoids a segmentation fault when the blitter state
happens to be bound when the context is destroyed.

The free calls should probably removed altogether in the future -- the
responsibility to destroy the state atoms lies with whoever created it,
and the safest thing for the pipe driver is to not touch any bound state
in its destructor.
2010-11-03 20:25:13 +00:00
..
auxiliary scons: Revamp how to specify targets to build. 2010-11-01 13:30:22 +00:00
docs gallium: new CAP, state for primitive restart 2010-10-21 19:03:38 -06:00
drivers r600g: Swap the util_blitter_destroy call order. 2010-11-03 20:25:13 +00:00
include gallium: new CAP, state for primitive restart 2010-10-21 19:03:38 -06:00
state_trackers st/xorg: Detect libkms with scons too. 2010-11-03 15:21:51 +00:00
targets xorg/vmwgfx: Link libkms when available. 2010-11-03 15:41:06 +00:00
tests scons: Revamp how to specify targets to build. 2010-11-01 13:30:22 +00:00
tools u_debug_symbol: add support for getting symbol names from glibc 2010-08-20 18:18:28 +02:00
winsys r600g: set hardware pixel centers according to gl_rasterization_rules 2010-11-03 09:36:01 +00:00
Makefile gallium: Improve recursive makefiles 2009-02-20 11:25:55 +00:00
Makefile.template gallium: add $(PROGS_DEPS) as dependencies for $(PROGS) 2010-09-27 14:11:12 +02:00
README.portability gallium: refactor/replace p_util.h with util/u_memory.h and util/u_math.h 2008-08-24 17:48:55 -06:00
SConscript scons: i915 can't build on MSVC either. 2010-11-02 13:49:35 +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.

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