mesa/src/compiler/glsl/glcpp at 7fedf51b959e0d18cefff7b8556578279eab21f6 - mesa

Files

T

Michel Dänzer 7fedf51b95 glsl/tests: Use exit code 126 to detect valgrind errors

valgrind returns exit code 126 if it can't write to the file passed to
--log-file. Hopefully it'll be the same for any other invalid valgrind
command line parameters or internal errors as well.

Using a different exit code (31) for this was hiding the fact that the
valgrind test wasn't actually working.

v2:
* Use exit code 126; can't treat any non-0 exit code as failure because
  glcpp is expected to exit with non-0 for some of the input we feed it

Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>

2021-03-19 08:50:38 +00:00

tests

glsl/tests: Use exit code 126 to detect valgrind errors

2021-03-19 08:50:38 +00:00

glcpp-lex.l

glsl: add preprocessor #include support

2019-11-20 05:05:55 +00:00

glcpp-parse.y

glsl: add extra pp tokens workaround and enable for CoR

2020-10-29 23:35:58 +00:00

glcpp.c

glcpp: Fully initialize struct gl_context

2021-03-19 08:50:37 +00:00

glcpp.h

glsl: add preprocessor #include support

2019-11-20 05:05:55 +00:00

meson.build

glsl/tests: Bump glcpp valgrind test timeout to 240 seconds

2021-03-19 08:50:37 +00:00

pp_standalone_scaffolding.c

mesa: add support cursor support for relative path shader includes

2019-11-20 05:05:56 +00:00

pp_standalone_scaffolding.h

mesa: add support cursor support for relative path shader includes

2019-11-20 05:05:56 +00:00

pp.c

glsl: pass gl_context to glcpp_parser_create()

2019-11-20 05:05:55 +00:00

README

…

README

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