mesa/tests/glcpp-test

#!/bin/sh

for test in *.c; do
    echo "Testing $test"
    ../glcpp < $test > $test.glcpp
    grep -v '^$' < $test.glcpp > $test.out || true
    gcc -E $test -o $test.gcc
    grep -v '^#' < $test.gcc | grep -v '^$' > $test.expected || true
    diff -u $test.expected $test.out
done
Add a very simple test for the pre-processor. Validate desired test cases by ensuring the output of glcpp matches the output of the gcc preprocessor, (ignoring any lines of the gcc output beginning with '#'). Only one test case so far with a trivial #define. 2010-05-10 16:21:10 -07:00			`#!/bin/sh`
Starting over with the C99 grammar for the preprocessor. This is a fresh start with a much simpler approach for the flex/bison portions of the preprocessor. This isn't functional yet, (produces no output), but can at least read all of our test cases without any parse errors. The grammar here is based on the grammar provided for the preprocessor in the C99 specification. 2010-05-25 13:09:03 -07:00
Add a very simple test for the pre-processor. Validate desired test cases by ensuring the output of glcpp matches the output of the gcc preprocessor, (ignoring any lines of the gcc output beginning with '#'). Only one test case so far with a trivial #define. 2010-05-10 16:21:10 -07:00			`for test in *.c; do`
			`echo "Testing $test"`
Remove blank lines from output files before comparing. Recently I'm seeing cases where "gcc -E" mysteriously omits blank lines, (even though it prints the blank lines in other very similar cases). Rather than trying to decipher and imitate this, just get rid of the blank lines. This approach with sed to kill the lines before the diff is better than "diff -B" since when there is an actual difference, the presence of blank lines won't make the diff harder to read. 2010-05-27 14:53:51 -07:00			`../glcpp < $test > $test.glcpp`
			`grep -v '^$' < $test.glcpp > $test.out \|\| true`
Add a very simple test for the pre-processor. Validate desired test cases by ensuring the output of glcpp matches the output of the gcc preprocessor, (ignoring any lines of the gcc output beginning with '#'). Only one test case so far with a trivial #define. 2010-05-10 16:21:10 -07:00			`gcc -E $test -o $test.gcc`
Remove blank lines from output files before comparing. Recently I'm seeing cases where "gcc -E" mysteriously omits blank lines, (even though it prints the blank lines in other very similar cases). Rather than trying to decipher and imitate this, just get rid of the blank lines. This approach with sed to kill the lines before the diff is better than "diff -B" since when there is an actual difference, the presence of blank lines won't make the diff harder to read. 2010-05-27 14:53:51 -07:00			`grep -v '^#' < $test.gcc \| grep -v '^$' > $test.expected \|\| true`
			`diff -u $test.expected $test.out`
Add a very simple test for the pre-processor. Validate desired test cases by ensuring the output of glcpp matches the output of the gcc preprocessor, (ignoring any lines of the gcc output beginning with '#'). Only one test case so far with a trivial #define. 2010-05-10 16:21:10 -07:00			`done`