mesa/src/gallium
Marek Olšák 597b9e8810 radeonsi/gfx9: work around a GPU hang due to broken indirect indexing in LLVM
Fixes: 6d19120da8 "radeonsi/gfx9: workaround for INTERP with indirect indexing"
Cc: 18.1 <mesa-stable@lists.freedesktop.org>
Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>
2018-05-10 18:26:32 -04:00
..
auxiliary gallium/auxiliary: Add helper function to count the number of entries in hash table 2018-05-10 05:12:43 -04:00
docs gallium: add initial support for conservative rasterization 2018-04-30 21:13:53 -06:00
drivers radeonsi/gfx9: work around a GPU hang due to broken indirect indexing in LLVM 2018-05-10 18:26:32 -04:00
include gallium: add initial support for conservative rasterization 2018-04-30 21:13:53 -06:00
state_trackers clover: Add explicit virtual destructor to argument class 2018-05-05 13:17:08 -04:00
targets meson: fix graw-xlib after auxiliary consolidation 2018-04-24 14:08:15 -07:00
tests gallium/tests: Fix assignment of EXTRA_DIST 2018-05-09 16:38:47 -07:00
tools gallium/tools: use correct shebang for python scripts 2017-03-10 14:12:47 +00:00
winsys winsys/radeon: Destroy fd_hash table when the last winsys is removed. 2018-05-10 05:12:48 -04:00
Android.common.mk Android: rework LLVM build support 2017-05-11 13:52:21 +01:00
Android.mk radeonsi: try to fix android 2018-04-05 15:34:58 -04:00
Automake.inc radeonsi: prepare for driver-specific driconf options 2017-08-02 09:50:58 +02:00
Makefile.am autotools: Include new meson files 2018-04-20 20:26:56 -07:00
meson.build meson: raise required version to 0.44.1 2018-04-24 14:08:15 -07:00
README.portability
SConscript gallium: move ddebug, noop, rbug, trace to auxiliary to improve build times 2018-04-13 14:08:14 -04: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.