diff options
author | Carl Worth <[email protected]> | 2014-06-11 18:02:54 -0700 |
---|---|---|
committer | Carl Worth <[email protected]> | 2014-07-09 12:05:13 -0700 |
commit | 1d862a0b39dfd2723aac6c64f9a7609c205b3cdc (patch) | |
tree | 3a1e750d5abdcca7f25187fbf70adf65c947449b /src/glsl/glcpp/tests/030-define-chain-obj-to-func-compose.c.expected | |
parent | a6e9cd14cad555520ad98213adf541a7687a7498 (diff) |
glsl/glcpp: Fixup glcpp tests for redefining a macro with whitespace changes.
Previously, the test suite was expecting the compiler to allow a redefintion
of a macro with whitespace added, but gcc is more strict and allows only for
changes in the amounts of whitespace, (but insists that whitespace exist or
not in exactly the same places).
See: https://gcc.gnu.org/onlinedocs/cpp/Undefining-and-Redefining-Macros.html:
These definitions are effectively the same:
#define FOUR (2 + 2)
#define FOUR (2 + 2)
#define FOUR (2 /* two */ + 2)
but these are not:
#define FOUR (2 + 2)
#define FOUR ( 2+2 )
#define FOUR (2 * 2)
#define FOUR(score,and,seven,years,ago) (2 + 2)
This change adjusts the existing "redefine-macro-legitimate" test to work with
the more strict understanding, and adds a new "redefine-whitespace" test to
verify that changes in the position of whitespace are flagged as errors.
Reviewed-by: Anuj Phogat <[email protected]>
Diffstat (limited to 'src/glsl/glcpp/tests/030-define-chain-obj-to-func-compose.c.expected')
0 files changed, 0 insertions, 0 deletions