From: <no...@so...> - 2001-05-10 13:49:36
|
Bugs item #422564, was updated on 2001-05-09 00:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105523&aid=422564&group_id=5523 Category: None Group: Execution Error Status: Open Resolution: None >Priority: 8 Submitted By: Navindra Umanee (navindra) >Assigned to: Etienne M. Gagnon (egagnon) Summary: Switch statement not handled correctly Initial Comment: Aha! Found my second or third SableVM bug -- finally one that's easy to describe and reproduce. ;-) Check the attached .java file, and compile it. Run it against Sun Java and SableVM: [asimov] [/home/navindra/work] java SableVMBug Switch1: 1 [asimov] [/home/navindra/work] sablevm -Y SableVMBug Switch1: default While debugging coffi, I at first thought this bug involved nested switches but the simplicity of this included example proves otherwise and muchly confuses me. It appears that sometimes switches work and sometimes not. I'll look into this some more if it'll help. ---------------------------------------------------------------------- Comment By: Navindra Umanee (navindra) Date: 2001-05-09 00:59 Message: Logged In: YES user_id=210140 It's more interesting than I thought. The problem exhibits itself if one uses the Sun Java compiler to compile the attached file, but not if one uses the Jikes compiler with the SablePath libraries. The most interesting difference in the compiled code is that Jikes uses a Tableswitch where javac uses a Lookupswitch. Hmmm. Must sleep. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105523&aid=422564&group_id=5523 |