[PATCH] analyzer/pr94028.C and non-null warning

[David Edelsohn via Gcc-patches]

The changes to the non-null warning now produce an additional warning
for analyzer/pr94028.C on one of the "leak" lines.  This causes new
failures on trunk.

Because non-null is not the purpose of the analyzer test, I propose
pruning the output to resolve the new failures.  Alternatively, I
could explicitly test for the additional non-null warning.

Do you have any preferences?

I propose appending

// { dg-prune-output "where non-null expected" }

to the file to prune the warning output.

Thanks, David