mesa/src/gallium
Ilia Mirkin f317f72f73 r600g: use SIMPLE_FLOAT for blending to enable some optimizations
Radeonsi also sets this flag. Seems to avoid pulling up the desintation
RT value when the dst blend factor is zero if it's not otherwise being
loaded. Among other things, it allows blending to overwrite infinity/NaN
values in the destination RT.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Roland Scheidegger <sroland@vmware.com>
Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>
2017-11-08 22:35:27 -05:00
..
auxiliary gallivm: Use new LLVM fast-math-flags API 2017-11-08 10:44:19 +01:00
docs gallium: add PIPE_CAP_SIGNED_VERTEX_BUFFER_OFFSET 2017-11-06 19:09:12 +01:00
drivers r600g: use SIMPLE_FLOAT for blending to enable some optimizations 2017-11-08 22:35:27 -05:00
include gallium: Wire up flush control 2017-11-06 16:09:03 -05:00
state_trackers mesa: use simple mtx in core mesa 2017-11-09 12:07:48 +11:00
targets targets/opencl: don't hardcode the icd file install to /etc/... 2017-11-08 14:10:07 +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 amdgpu: use simple mtx 2017-11-09 12:07:48 +11: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
meson.build meson: build gallium based osmesa 2017-10-27 11:06:45 -07:00
README.portability
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.