mesa/src/gallium
Luca Barbieri 10adb7840c translate: allow clients to ask for supported output formats
Currently translate asserts on unsupported output formats, making
it impossible to use for some purposes, such as testing whether it
actually works on all formats it supports.

Removing the assert was met with opposition, so this change allows
clients to ask whether an output format is supported, and they are thus
able to avoid attempting to use it.

Since this is just an addition to the API, no adverse effect is
possible, and it makes the testsuite work again.
2010-08-11 21:47:27 +02:00
..
auxiliary translate: allow clients to ask for supported output formats 2010-08-11 21:47:27 +02:00
docs docs: clarify point sprite discussion 2010-08-05 11:09:14 +01:00
drivers r300/compiler: Implement the CONT opcode. 2010-08-11 11:39:57 -07:00
include gallium: add ALWAYS_INLINE 2010-08-11 11:27:46 +02:00
state_trackers st/dri: fix crash when dri2_drawable_get_buffers fails 2010-08-04 00:07:28 +02:00
targets targets/egl: Fix build by including missing headers. 2010-08-06 11:46:16 -07:00
tests translate: Add translate_test.c to SCons. 2010-08-11 12:18:25 -07:00
winsys svga: Remove unnecessary headers. 2010-08-10 17:53:08 -07:00
Makefile gallium: Improve recursive makefiles 2009-02-20 11:25:55 +00:00
Makefile.template gallium: Fix build with llvm installed in non-standard location 2010-07-23 23:38:07 +01: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 graw: update graw_null after interface changes and build graw tests again 2010-06-07 16:43:49 +01: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.