[Bug 145] Java volatile and final access flags are ignored, except in reflection

[email protected] Mon, 11 Jul 2005 17:56:22 -0400

Newsgroups	gmane.comp.java.vm.sablevm.bugs
Message-ID	<[email protected]>

http://sablevm.org/bugs/show_bug.cgi?id=145

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |92
              nThis|                            |
         AssignedTo|[email protected]    |[email protected]
             Status|ASSIGNED                    |NEW
            Summary|Java volatile access flag is|Java volatile and final
                   |ignored                     |access flags are ignored,
                   |                            |except in reflection



------- Additional Comments From [email protected]  2005-07-11 17:56 -------
How should I treat volatiles and finals in SableVM, with respect to method
preparation?  Do we need new (GET|PUT)(FIELD|STATIC)_(FINAL|VOLATILE)_<X>
instructions?  This would probably be the most beneficial for the inlined
threaded engine -- no need to branch on access flags being set, and no need to
modify the instruction layout.  I would use macros to reduce human code
duplication.  NB: final and volatile flags are mutex.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.