Abstract: The present disclosure relates to an attempted optimized code layout utilizing a runtime managed environment and, more specifically, to attempting to optimize the layout of code, which utilizes a runtime managed environment, by attempting to place both callee and caller addresses within the same memory segment.

Abstract: Lock reservation methods and apparatus for multi-threaded environments are disclosed. An example method disclosed herein comprises determining whether the thread is a lock reservation owner of a lock corresponding to the object, at least one of acquiring the lock and releasing the lock if the thread is the lock reservation owner, and directing the lock reservation owner to unreserve the lock if the thread is not the lock reservation owner.

Abstract: Disclosed are a method, apparatus and system for dynamically managing layout of compiled code in a managed runtime environment. Profile feedback is generated during runtime, based on hardware event data that is gathered during runtime. A code manager dynamically relocates compiled code to reduce miss events based on the profile feedback. The code manager may also relocate virtual method tables in a virtual table region in order to reduce data miss events. The method does not require a prior run of an application program because profile feedback is based on event data that is tracked by hardware during execution of the software application and is not based on instrumented code.

Abstract: A runtime environment is described that includes a locking module to reserve a lock of an object among a plurality of reserved states when an external thread wants to access the object, and to unreserve the lock to an unreserved state when another external thread wants to access the object. The runtime environment further includes a lock re-reservation module to re-reserve the lock from the unreserved state to a first reserved state when the lock is in the unreserved state. A method of re-reserving a lock of an object is also described.