Abstract: A JIT (Just-In-Time) compiler performs dual-mode code generation by determining whether an application has opted-in to SIMD (Single Instruction Multiple Data) code generation both at JIT-time and at runtime. The application may select the code generation mode by identifying whether it has opted-in to SIMD code generation. As a result, the underlying implementation guarantees application compatibility by allowing the application to select the code generation mode. Additionally, applications have the ability to select into different code generation modes during concurrent execution.

Abstract: A JIT (Just-In-Time) compiler performs dual-mode code generation by determining whether an application has opted-in to SIMD (Single Instruction Multiple Data) code generation both at JIT-time and at runtime. The application may select the code generation mode by identifying whether it has opted-in to SIMD code generation. As a result, the underlying implementation guarantees application compatibility by allowing the application to select the code generation mode. Additionally, applications have the ability to select into different code generation modes during concurrent execution.

Abstract: Just in time compiled code and other data within a runtime environment may be shared between multiple applications by identifying common data objects and allowing two or more applications to access the data objects. While at least one application is accessing the objects, the objects may remain in memory. When all applications have stopped accessing an object, the object may be removed from memory. One embodiment may use a server process to manage various operations to facilitate sharing between various applications, such as identifying objects that may be removed from memory and adding newly created data to a database of sharable data.

Abstract: Just in time compiled code and other data within a runtime environment may be shared between multiple applications by identifying common data objects and allowing two or more applications to access the data objects. While at least one application is accessing the objects, the objects may remain in memory. When all applications have stopped accessing an object, the object may be removed from memory. One embodiment may use a server process to manage various operations to facilitate sharing between various applications, such as identifying objects that may be removed from memory and adding newly created data to a database of sharable data.

Abstract: In one or more embodiments, driver files are assigned strongly-named locations in a system directory. Different versions of driver files are assigned their own different, strongly-named locations. By assigning different versions of driver files to different strongly-named locations, different versions of the same driver file can be installed, managed, and upgraded without loss of functionality associated with other installed driver file versions. In at least some embodiments, a text file includes named sections that direct installation of a particular driver package. The text file can include a list of file dependencies that enable files to be associated with individual strongly-named locations.