This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] [JAVA] don't use UINT32 and UINT64 in interpret.cc

From: Tom Tromey <tromey at redhat dot com>
To: Andreas Schwab <schwab at suse dot de>
Cc: bonzini at gnu dot org, Gcc Patch List <gcc-patches at gcc dot gnu dot org>
Date: 14 Oct 2003 09:58:14 -0600
Subject: Re: [PATCH] [JAVA] don't use UINT32 and UINT64 in interpret.cc
References: <3F8C16BE.1060509@polimi.it> <87ptgz3jty.fsf@fleche.redhat.com><jer81fajsk.fsf@sykes.suse.de>
Reply-to: tromey at redhat dot com

>>>>> "Andreas" == Andreas Schwab <schwab@suse.de> writes:

>> How about using unsigned jint and unsigned jlong?

Andreas> Doesn't work with typedefs.

Now that my daily dose of ignorance is out on the table...

We've already got _Jv_uint in javaprims.h.  We might as well add
_Jv_ulong.

Tom

Follow-Ups:
- Re: [PATCH] [JAVA] don't use UINT32 and UINT64 in interpret.cc
  - From: Paolo Bonzini

References:
- [PATCH] [JAVA] don't use UINT32 and UINT64 in interpret.cc
  - From: Paolo Bonzini
- Re: [PATCH] [JAVA] don't use UINT32 and UINT64 in interpret.cc
  - From: Tom Tromey
- Re: [PATCH] [JAVA] don't use UINT32 and UINT64 in interpret.cc
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]