mesa/src/gallium
Roland Scheidegger 67906f91c9 llvmpipe: first steps of adding dual source blend support
This adds support of the additional blending factors to the blend function
itself, and also enables testing of it in lp_test_blend (which passes).
Still need to add the glue code of linking fs shader outputs to blend inputs
in llvmpipe, and probably need to add special handling if destination doesn't
include alpha (which lp_test_blend doesn't test).

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
2013-02-08 16:32:30 -08:00
..
auxiliary gallium: add RGBX formats for existing GL RGB texture formats 2013-02-07 00:20:23 +01:00
docs gallium: add SQRT shader opcode 2013-02-04 09:33:44 -07:00
drivers llvmpipe: first steps of adding dual source blend support 2013-02-08 16:32:30 -08:00
include gallium: add RGBX formats for existing GL RGB texture formats 2013-02-07 00:20:23 +01:00
state_trackers xorg: fix exa finish access 2013-02-08 19:01:19 -05:00
targets libgl-xlib/build: Link with C++ when LLVM is used 2013-01-24 14:00:27 -08:00
tests gallium/util: fix glClear with MRT by making the FS write to all cbufs 2013-01-15 16:47:18 +01:00
tools trace: measure time for each gallium call 2013-02-01 08:00:28 -07:00
winsys radeonsi: add support for Oland chips 2013-02-04 15:43:21 -05:00
Android.common.mk
Android.mk radeonsi: initial WIP SI code 2012-04-13 10:32:06 -04:00
Automake.inc Remove MESA_PIC_FLAGS macro 2013-01-10 22:01:31 +01:00
Makefile.am automake: Convert src/gallium/Makefile to automake. 2012-06-21 10:08:26 -07:00
README.portability
SConscript scons: Fix SCons build infrastructure for FreeBSD. 2012-05-24 18:49:40 -07: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.