Commit baa17c87 authored by Carl Worth's avatar Carl Worth

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.
parent 050e3ded
......@@ -6,4 +6,5 @@ glcpp-parse.h
......@@ -3,8 +3,9 @@ set -e
for test in *.c; do
echo "Testing $test"
../glcpp < $test > $test.out
../glcpp < $test > $test.glcpp
grep -v '^$' < $test.glcpp > $test.out || true
gcc -E $test -o $test.gcc
grep -v '^#' < $test.gcc > $test.expected
diff -B -u $test.expected $test.out
grep -v '^#' < $test.gcc | grep -v '^$' > $test.expected || true
diff -u $test.expected $test.out
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment