mesa/src/glsl/glcpp
Dave Airlie 277f4d75a7 glsl: add ARB_gpu_shader_fp64 to the glsl extensions. (v2)
v2: add define bit (Tapani Pälli)

Patch makes following Piglit tests pass:
   arb_gpu_shader_fp64/preprocessor/define.vert
   arb_gpu_shader_fp64/preprocessor/define.frag

Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
2015-02-19 00:28:33 -05:00
..
tests glcpp: Make tests write .out files to builddir. 2014-12-12 12:11:50 -08:00
.gitignore glcpp: Add back tests/*.out to .gitignore 2013-01-11 11:49:33 +01:00
glcpp-lex.l glcpp: Don't use alternation in the lookahead for empty pragmas. 2014-08-22 15:14:59 -07:00
glcpp-parse.y glsl: add ARB_gpu_shader_fp64 to the glsl extensions. (v2) 2015-02-19 00:28:33 -05:00
glcpp.c glcpp: Silence GCC warning 2015-02-17 12:29:58 -08:00
glcpp.h util: Move ralloc to a new src/util directory. 2014-08-04 11:06:58 -07:00
pp.c glsl/glcpp: Fix line-continuation code to handle multiple newline flavors 2014-08-07 16:08:29 -07:00
README glcpp: Update README for new support of __LINE__ and __FILE__. 2012-11-29 13:03:02 -08:00

glcpp -- GLSL "C" preprocessor

This is a simple preprocessor designed to provide the preprocessing
needs of the GLSL language. The requirements for this preprocessor are
specified in the GLSL 1.30 specification availble from:

http://www.opengl.org/registry/doc/GLSLangSpec.Full.1.30.10.pdf

This specification is not precise on some semantics, (for example,
#define and #if), defining these merely "as is standard for C++
preprocessors". To fill in these details, I've been using a draft of
the C99 standard as available from:

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf

Any downstream compiler accepting output from glcpp should be prepared
to encounter and deal with the following preprocessor macros:

	#line
	#pragma
	#extension

All other macros will be handled according to the GLSL specification
and will not appear in the output.

Known limitations
-----------------
A file that ends with a function-like macro name as the last
non-whitespace token will result in a parse error, (where it should be
passed through as is).