To trigger the bug, it suffices to have a line-continuation followed by a newline and then a non-line-continuation backslash. --- ...117-line-continuation-and-non-continuation-backslash.c | 12 ++++++++++++ ...continuation-and-non-continuation-backslash.c.expected | 13 +++++++++++++ 2 files changed, 25 insertions(+) create mode 100644 src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c create mode 100644 src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c.expected
diff --git a/src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c b/src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c new file mode 100644 index 0000000..6a6f282 --- /dev/null +++ b/src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c @@ -0,0 +1,12 @@ +/* This test case is the minimal case to replicate the bug reported here: + * + * https://bugs.freedesktop.org/show_bug.cgi?id=65112 + * + * To trigger the bug, there must be a line-continuation sequence + * (backslash newline), then an additional newline character, and + * finally another backslash that is not part of a line-continuation + * sequence. + */ +\ + +/* \ */ diff --git a/src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c.expected b/src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c.expected new file mode 100644 index 0000000..9b3eb67 --- /dev/null +++ b/src/glsl/glcpp/tests/117-line-continuation-and-non-continuation-backslash.c.expected @@ -0,0 +1,13 @@ + + + + + + + + + + + + + -- 1.7.10.4 _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
