jcf-write.c (OP2, OP4): Use "_i", not "_I" to avoid problems on FreeBSD.

* jcf-write.c (OP2, OP4): Use "_i", not "_I" to avoid problems on
        FreeBSD.

From-SVN: r22698
This commit is contained in:
Jeffrey A Law 1998-09-30 19:55:42 +00:00 committed by Jeff Law
parent aa90b11170
commit 4f01de5c33
2 changed files with 8 additions and 3 deletions

View file

@ -1,3 +1,8 @@
Wed Sep 30 20:53:51 1998 Jeffrey A Law (law@cygnus.com)
* jcf-write.c (OP2, OP4): Use "_i", not "_I" to avoid problems on
FreeBSD.
Thu Sep 17 19:45:01 1998 Jeffrey A Law (law@cygnus.com)
* Makefile.in (jcf-dump, jvgenmain): Link in memmove.o too.

View file

@ -52,13 +52,13 @@ struct buffer bytecode = NULL_BUFFER;
/* Like OP1, but I is a 2-byte big endian integer. */
#define OP2(I) \
do { int _I = (I); OP1 (_I >> 8); OP1 (_I); } while (0)
do { int _i = (I); OP1 (_i >> 8); OP1 (_i); } while (0)
/* Like OP1, but I is a 4-byte big endian integer. */
#define OP4(I) \
do { int _I = (I); OP1 (_I >> 24); OP1 (_I >> 16); \
OP1 (_I >> 8); OP1 (_I); } while (0)
do { int _i = (I); OP1 (_i >> 24); OP1 (_i >> 16); \
OP1 (_i >> 8); OP1 (_i); } while (0)
/* The current stack size (stack pointer) in the current method. */