Using a common reference address when processing calls among a native ABI and a foreign ABI. Based on caller calling using a reference address, a lookup structure is used to determine whether the reference address is within a memory range storing native code (and that the callee is native) or a memory range not storing native code (and that the callee is foreign). Execution of the callee is initiated based on one of (i) when the caller is native and when the callee is foreign, calling the callee using the reference address within an emulator; (ii) when the caller is foreign and the callee is native, calling an entry thunk; (iii) when the caller is native and the callee is foreign, calling an exit thunk; or (iv) when the caller is native and the callee is native, directly calling the callee using the reference address.

Platform-agnostic model source code may refer to a file that includes platform-agnostic notations and source code according to a programming language. The source code may lack explicit references to specific computing resource service providers. The platform-agnostic model source code may be parsed to determine a set of computing resources of a computing resource service provider to provision. The set of computing resources may be provisioned and exposed via an endpoint. The platform-agnostic notations may be used to determine addition source code according to the programming language that can be used to access the set of computing resources. A runtime (e.g., software application) may be generated from the source code and the additional source code such that the execution of the runtime utilizes at least a portion of the set of computing resources.

A collection of code fragments loaded in an interactive development platform for running on a first processor can be received. A candidate fragment in the collection of code fragments can be determined for migration to a second processor based on characterizing the collection of code fragments. Based on a location of the candidate fragment in the collection of code fragments, a spot can be identified in the collection of code fragments to inject a code for saving program context. The code for saving program context can be injected in the identified spot. Responsive to the code for saving program context having run on the first processor and based on a criterion, the program context can be migrated to the second processor.

A method and an apparatus that schedule a plurality of executables in a schedule queue for execution in one or more physical compute devices such as CPUs or GPUs concurrently are described. One or more executables are compiled online from a source having an existing executable for a type of physical compute devices different from the one or more physical compute devices. Dependency relations among elements corresponding to scheduled executables are determined to select an executable to be executed by a plurality of threads concurrently in more than one of the physical compute devices. A thread initialized for executing an executable in a GPU of the physical compute devices are initialized for execution in another CPU of the physical compute devices if the GPU is busy with graphics processing threads. Sources and existing executables for an API function are stored in an API library to execute a plurality of executables in a plurality of physical compute devices, including the existing executables and online compiled executables from the sources.

Using a common reference address when processing calls among a native ABI and a foreign ABI. Based on caller calling using a reference address, a lookup structure is used to determine whether the reference address is within a memory range storing native code (and that the callee is native) or a memory range not storing native code (and that the callee is foreign). Execution of the callee is initiated based on one of (i) when the caller is native and when the callee is foreign, calling the callee using the reference address within an emulator; (ii) when the caller is foreign and the callee is native, calling an entry thunk; (iii) when the caller is native and the callee is foreign, calling an exit thunk; or (iv) when the caller is native and the callee is native, directly calling the callee using the reference address.

A system comprising one or more computers implements a virtual domain control unit/virtual electronic control unit service configured to deploy vehicle code packages to one or more of a plurality of supported virtual domain control unit/electronic control unit orchestration environments, which include both a local orchestration environment and one or more remote orchestration environments. In such orchestration environments, virtual domain control units and/or virtual electronic control units are implemented that execute code included in the vehicle code packages. In some embodiments, such virtual domain control units or virtual electronic control units allow computing capacity and/or data storage capacity of a vehicle to be augmented via remotely implemented virtual domain control units and/or remotely implemented virtual electronic control units.

A client server environment having a server with a Web service in communication with a local client application which is tightly integrated with its local operating environment residing on a platform remote from the server; the local client application tightly integrated by way of integrating data structures requested and received from the server; the integrating data structures defining the attributes and parameters needed by the local client application to define an interface between the local client application and the Web service. The integrating data structures enable tight/close integration between the hosted application and the devices and the operating system features of the platform upon which the local client application resides. Also disclosed is an abstracted environment which can run on any one of the supported platform's devices as a native application, all based on the passing of the same page commands and receipt of corresponding client data objects.

Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.

In accordance with one or more aspects, a request to run an application is received. The application has an associated tune manifest that identifies one or more resources that the application may use. The tune manifest is compared to a device resource record, and a check is made, based at least in part on the comparing, whether the one or more resources identified in the tune manifest can be satisfied by the device. If the one or more resources identified in the tune manifest can be satisfied by the device, then the application is run; otherwise, a notification of a conflict between the application and the device is presented. Additionally, when the application exits, a device tune state that identifies a content source to which the device was tuned prior to running the application can be retrieved and the device restored to this device tune state.