Re: Java encryption implementation

From: Mike Amling (nospam_at_icic.gov.ir)
Date: 11/29/05 

Date: Tue, 29 Nov 2005 01:38:00 GMT

Gregory G Rose wrote:
>
> [*] does Java guarantee 64-bit longs? I'm not
> sure. In C/C++, this could give you either 48, 32,
> or even 16 meaningful bits in "seed".

   Yes. A Java long is always exactly 64 signed bits, an int is 32
signed bits, a short is 16 signed bits, a char is 16 unsigned bits, a
byte is 8 signed bits, a float is IEEE 32-bit and a double is IEEE
64-bit, regardless of platform or version.

--Mike Amling

Relevant Pages

  • Re: after SIMD implementation, is it still a RISC?
    ... |>> Abolish arithmetic exceptions, just as Java has? ... |>> neat way of providing an extra facility for no extra ISA. ... taking the IEEE 754, Java and C99 approaches to their limit. ...
    (comp.arch)
  • Re: Source code for native methods in java
    ... least for the subset of functionalities used by Java (no IEEE ... "exceptions", only one rounding mode). ... For a plain Java SE from Sun and a system really lacking hardware ... Of course, a kernel trap is very expensive, so the "five times slower" ...
    (comp.lang.java.programmer)
  • Re: Source code for native methods in java
    ... You can get the definition of it in the upcoming Java 7 from ... What if the native representation of floats isn't IEEE ... since it couldn't use the native floating point anyway. ... (I believe some of the Java ME standard allows no FP) ...
    (comp.lang.java.programmer)
  • Re: double cast to int reliable?
    ... If int is 32 bits no. ... A IEEE double can hold 53 bits of precision ... deal with non-IEEE floating point formats. ... match IEEE requirements, but do meet the requirements of the C ...
    (comp.lang.c)
  • Re: Source code for native methods in java
    ... What if the native representation of floats isn't IEEE ... I'd be curious to know if there are any conformant Java ... since it couldn't use the native floating point anyway. ...
    (comp.lang.java.programmer)