mesa/src/gallium
Charmaine Lee 043883647a st/wgl: flush with ST_FLUSH_WAIT before releasing shared contexts
Before releasing a shared context, flush the context
with ST_FLUSH_WAIT to make sure all commands are executed.
This ensures that rendering to any shared resources is completed
before they will be referenced by another context.

Fixes an intermittent flickering with Photoshop. (VMware bug# 1779340)

Reviewed-by: Brian Paul <brianp@vmware.com>
2017-02-18 09:36:42 -08:00
..
auxiliary vl: u_upload_alloc might fail to allocate buffer in bicubic filter 2017-02-22 21:49:19 +01:00
docs gallium: add get_disk_shader_cache() callback 2017-02-23 09:20:22 +11:00
drivers radeon: fix r600 builds when old version of llvm is present 2017-02-23 14:05:55 +11:00
include gallium: add get_disk_shader_cache() callback 2017-02-23 09:20:22 +11:00
state_trackers st/wgl: flush with ST_FLUSH_WAIT before releasing shared contexts 2017-02-18 09:36:42 -08:00
targets gallium: Remove vc4 simulator hack from loader infrastructure. 2017-02-06 12:44:06 -08:00
tests gallium: let state trackers tell u_vbuf whether user VBOs are possible 2017-02-14 21:47:51 +01:00
tools
winsys gallium/u_queue: isolate util_queue_fence implementation 2017-02-22 20:26:39 +01:00
Android.common.mk android: fix llvm, elf dependencies for M, N releases 2017-02-01 23:01:35 +00:00
Android.mk ilo: EOL drop unmaintained gallium drv from buildsys 2017-02-03 16:13:36 +11:00
Automake.inc gallium: correctly manage libsensors link flags 2017-01-18 16:01:14 +00:00
Makefile.am ilo: EOL drop unmaintained gallium drv from buildsys 2017-02-03 16:13:36 +11:00
README.portability gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
SConscript gallium: swr: Added swr build for windows 2016-11-21 12:44:47 -06: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.

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