Date: Sun, 1 Jun 1997 22:31:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: ucd-snmp-3.1.3 doesn't like FreeBSD3? Message-ID: <19970601223118.VX29490@uriah.heep.sax.de> In-Reply-To: <17191.865192920@orion.webspan.net>; from Gary Palmer on Jun 1, 1997 15:22:00 -0400 References: <199706010818.BAA14119@rah.star-gate.com> <17191.865192920@orion.webspan.net>
next in thread | previous in thread | raw e-mail | index | archive | help
As Gary Palmer wrote:
> > cc -I.. -O2 -pipe -Dfreebsd3 -c md5.c
> > md5.c: In function `MDblock':
> > md5.c:157: warning: decimal constant is so large that it is unsigned
> > md5.c:158: warning: decimal constant is so large that it is unsigned
> Those warnings have been there since day one. I have no idea if they
> mean anything or not
They simply mean someone defined a constant that would have the sign
bit set, but it wasn't declared to be a negative constant. You could
supposedly get around this by appending a `U' to the constant (thus
indicating to the compiler that it is really meant to be unsigned).
Seems gcc does already believe into the good intentions of the
programmer if he used a hexadecimal constant:
j@uriah 405% cat > foo.c
int
main(void)
{
unsigned a, b;
a = 0xd76aa478;
b = 3614090360;
return 0;
}
^D
j@uriah 406% cc -Wall foo.c
foo.c: In function `main':
foo.c:7: warning: decimal constant is so large that it is unsigned
Both values above are identical. Appending the `U' silences the
warning, of course.
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970601223118.VX29490>