Clone of mesa.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Vinson Lee 95cb6d30ae r600g: Remove unused variable. преди 15 години
..
auxiliary util: fix util_pack_color for B4G4R4A4 преди 15 години
docs gallium/docs: The RET opcode may appear anywhere in a subroutine. преди 15 години
drivers r600g: Remove unused variable. преди 15 години
include dri: Pass the __DRIscreen and the __DRIscreen private back to image lookup преди 15 години
state_trackers d3d1x: CRLF -> LF in progs преди 15 години
targets r600g: set back to correct codepaths. преди 15 години
tests util: Flush stdout on util_format. преди 15 години
tools u_debug_symbol: add support for getting symbol names from glibc преди 15 години
winsys r600g: bring over fix from old path to new path преди 15 години
Makefile gallium: Improve recursive makefiles преди 16 години
Makefile.template gallium: Fix build with llvm installed in non-standard location преди 15 години
README.portability gallium: refactor/replace p_util.h with util/u_memory.h and util/u_math.h преди 17 години
SConscript graw: update graw_null after interface changes and build graw tests again преди 15 години

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.

* Don't use the 'inline' keyword, use the INLINE macro in p_compiler.h instead.

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