mesa/src/gallium
Wladimir J. van der Laan 0ba4320d94 etnaviv: Allow clearing constant buffer using buffer==NULL user_buffer==NULL
Prevents an assertion when using GALLIUM_HUD with ioquake3,
when cso_restore_constant_buffer_slot0 restores an empty
constant buffer in slot 0.

Signed-off-by: Wladimir J. van der Laan <laanwj@gmail.com>
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
2017-11-02 11:03:30 +01:00
..
auxiliary meson: use dep_m in libgallium 2017-10-31 08:10:37 +01:00
docs gallium: add cap for driver specified max combined shader resources. 2017-11-01 10:07:03 +10:00
drivers etnaviv: Allow clearing constant buffer using buffer==NULL user_buffer==NULL 2017-11-02 11:03:30 +01:00
include gallium: increase pipe_sampler_view::target bitfield size for MSVC 2017-11-01 11:06:02 -06:00
state_trackers meson: build gallium based osmesa 2017-10-27 11:06:45 -07:00
targets Android: move drivers' symlinks to /vendor (v2) 2017-10-30 15:41:31 +00:00
tests gallium: Remove util_format_s3tc_init() 2017-10-02 19:41:22 -07:00
tools gallium/tools: use correct shebang for python scripts 2017-03-10 14:12:47 +00:00
winsys svga: Use __asm__ instead of asm 2017-11-01 15:05:26 -07:00
Android.common.mk Android: rework LLVM build support 2017-05-11 13:52:21 +01:00
Android.mk Android: fix build break from r600/radeon split 2017-10-10 21:37:19 -05:00
Automake.inc radeonsi: prepare for driver-specific driconf options 2017-08-02 09:50:58 +02:00
Makefile.am broadcom: Add V3D 3.3 gallium driver called "vc5", for BCM7268. 2017-10-10 11:42:04 -07:00
README.portability
SConscript gallium: swr: Added swr build for windows 2016-11-21 12:44:47 -06:00
meson.build meson: build gallium based osmesa 2017-10-27 11:06:45 -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.

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