mesa/src/gallium
Ilia Mirkin 8b76a3744c nv50/ir: fix bb positions after exit instructions
It's fairly rare that the BB layout puts BBs after the exit block, which
is likely the reason these issues lingered for so long.

This fixes a fraction of issues with the giant pixmark piano shader.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
Cc: <mesa-stable@lists.freedesktop.org>
(cherry picked from commit e988999791)
2016-09-01 11:39:42 +01:00
..
auxiliary gallium/util: add helper to compute zmin/zmax for a viewport state 2016-09-01 11:39:42 +01:00
docs gallium: Add a pipe cap for whether primitive restart works for patches. 2016-05-23 16:44:11 -07:00
drivers nv50/ir: fix bb positions after exit instructions 2016-09-01 11:39:42 +01:00
include Revert "gallium: Force blend color to 16-byte alignment" 2016-07-21 12:08:18 +01:00
state_trackers st/omx/enc: check uninitialized list from task release 2016-07-21 12:20:56 +01:00
targets gallium/dri: Add shared glapi to LIBADD on Android 2016-07-21 14:01:15 +01:00
tests scons: whitespace cleanup 2016-05-25 12:23:12 -06:00
tools
winsys winsys/amdgpu: disallow DCC with mipmaps 2016-07-27 14:37:01 +01:00
Android.common.mk android: enable the radeonsi driver 2015-06-09 12:25:50 -07:00
Android.mk virgl: also build vtest for Android 2016-02-02 09:58:51 +10:00
Automake.inc gallium: keep the libdrm link alongside libkmsdri.la 2015-11-21 12:52:18 +00:00
Makefile.am glx: Refactor the configure options for glx implementation choice (v3) 2016-05-01 08:37:25 +01:00
README.portability gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
SConscript scons: whitespace cleanup 2016-05-25 12:23:12 -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.