Details

    • Type: Improvement
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 2.9.2
    • Fix Version/s: 3.0
    • Component/s: Runtime
    • Labels:
      None

      Description

      Some code still assumes that the JTOC is not a constant. This adds noise to the code and creates confusion; as well, it can be an impediment when adding new code. In this improvement I will clean up the JTOC situation as much as possible, making it so that the native code assumes that it is a constant value that it acquires immediately upon loading, while the Java code has it as a baked-in constant. Notably, the baseline compiler on IA32 will no longer generate code to load the JTOC from the VM_Processor, and the VM_Processor will no longer have a JTOC field.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              No work has yet been logged on this issue.

                People

                • Assignee:
                  dgrove David Grove
                  Reporter:
                  pizlo Filip Pizlo
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: