This is almost certainly a sablevm bug, and not a classpath bug.
I've cc'ed the sablevm-bugs list.
--scott
On 10 Sep 2002, Emile Snyder wrote:
> Hi all,
>
> I'm using the 1.0.3 version of sablevm, and it's associated classpath.
> I haven't managed to get a CVS-checked-out version of classpath up and
> running with any VM yet. If this is fixed in the tree, or simply a VM
> issue I apologize in advance.
>
> The >>>= and >>> operators appear to be broken strangely. Demo class
> and output:
>
> ==============================================================
> import java.lang.*;
> import java.awt.color.*;
> import java.awt.image.*;
>
> public class ShiftBug {
> public static void main (String argv[])
> {
> long a = 0xff00;
> long b, c;
>
> b = a >>> 4;
> c = 0xff00 >>> 4;
> System.out.print (Long.toString(b,16) + " " + Long.toString(c,16) + "\n");
> }
> }
> ===================================================
>
> Output:
>
> [esnyder@basalt esnyder]$ jikes -classpath /usr/local/lib/sablevm/classes-1.0.3
>ShiftBug.java
> [esnyder@basalt esnyder]$ sablevm -Y ShiftBug
> ff000 ff0
>
> thanks,
> -emile
>
>
>
>
> _______________________________________________
> Classpath mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/classpath
>
>
strategic Treasury shotgun NRA Yeltsin Marxist plastique RNC explosion
corporate globalization Mossad Columbia Minister Boston Justice Shoal Bay
( http://cscott.net/ )
_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
