This is the mail archive of the
mailing list for the GCC project.
Re: buildfailure in expr.c on darwin
> that context it only caused one break in the testsuite, and I didn't
> check closely enough to know which of the numerous FAILs were my
i usually look here for the known (ie, not your fault) failures:
and when i'm lazy i do this to find out all the failures already there:
x="g++ gcc objc g++ g77"
for i in $x
lynx -source http://people.redhat.com/geoffk/gcc-regression/native-logsum/gcc/testsuite/$i.sum.gz | grep ^FAIL > /tmp/$$.poo
wc -l < /tmp/$$.poo
rm -f /tmp/*.poo
i'm sure there are better ways ;-)