In article <v03110719aff9e8ded2e3@[198.68.110.2]> fair@clock.org (Erik E. Fair  , Time Keeper) writes:
>Two systems: a SPARC LX and a Sun 3/60.
>Both sup'd -current as of this morning.
>
>In trying to build /usr/bin/pax, the SPARC is perfectly happy, and the Sun
>3/60 says:
>
>pushd /usr/src/bin/pax
>/usr/src/bin/pax /tmp
>root@chronos 59} make
>cc -O  -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  -c buf_subs.c
>cc1: warnings being treated as errors
>buf_subs.c: In function `appnd_start':
>buf_subs.c:240: warning: `cnt' might be used uninitialized in this function
>buf_subs.c: In function `rd_skip':
>buf_subs.c:443: warning: `cnt' might be used uninitialized in this function
>*** Error code 1
>
>Stop.
>21.0u 8.0s 0:37.74 77.0% 0+0k 223+40io 184pf+0w
>
>The compilers were both last installed on Jul 18 (the last time they both
>completed a build).
>
>BTW, the variable in question is uninitialized. Why does the Sun 3 catch
>it, and the Sun 4 ignore it, with identical sources and compile-time
>options?

I don't think it is uninitialized... Looks like a bug with long long variables
on the sun3.

christos