Abstract: According to the invention, a first executable environment is provided. The first executable environment is for execution within an operating system environment of a host computer system. The first executable environment is not an emulator for emulating any of another processor and another operating system. A software application is provided for installation and execution within the operating system environment. The software application is for fixed installation and not for installation in a portable fashion for being ported from one host computer system to another. The software application is then installed within the first executable environment, the installed software application installed within a removable peripheral memory storage device for execution within the first executable environment.

Abstract: Operating an integrated development environment in a data processing system comprising running a source code editor, displaying source code in a graphical interface of the source code editor, displaying at least one cross-reference marker, the at least one cross-reference marker indicating crosscutting in the source code, receiving an input, changing one or more cross-reference markers, and highlighting the one or more changed cross-reference marker.

Abstract: Systems and methods are provided for defining a default handler software application in response to an event at a computer. An event, for example, a user opening a file with a specific extension or accessing a uniform resource locator (URL) with a specific protocol, may trigger the operating system to instantiate a user-level default handler program associated with the event type and the specific user. Users may define user-level default handlers through a centralized user interface maintained by the operating system. During the application installation process, an application may register lists of supported events that the application is capable of handling.

Abstract: One embodiment of the present invention sets forth a system and method for implementing a scalable link interface (SLI) approval policy using a database. The resource manager within a GPU driver incorporates a database, which may be used to determine whether the current computer system configuration is approved for running in SLI mode. The database of specific approved configurations may be embedded within the GPU driver or stored in a separate file, which may be modified by an authorized user. The database may be encrypted to prevent unauthorized users from modifying to the database contents. When a given computer system configuration is an approved configuration within the database, the system may be enabled to operate in SLI mode.

Abstract: Mechanisms to support orphaned and partially configured objects are provided. A project includes a variety of objects. At least one object is designated as an orphaned object. The orphaned object lacks complete configuration details. Other objects of the project depend on the orphaned object and yet the other objects can load and process within the project as if the orphaned object was fully configured and available.

Abstract: A system and method for instrumenting program instructions. A processing system includes a compiler and a profiler. The profiler is configured to instrument an application by inserting one or more instrumentation instructions in the application. During execution of the application, execution is monitored and a particular condition is detected. Responsive to the condition, a portion of the code which corresponds to the detected condition is identified. A request is conveyed for recompilation of code which corresponds to code. Prior to recompilation of the code, the profiler instruments the portion of code. Execution and monitoring of the execution continue, and instrumentation/recompilation may be repeated. Initially, relatively little of the application code may be instrumented. As execution and monitoring continues, more and more of the application code may be dynamically instrumented during execution.

Abstract: Methods and apparatus, including computer program products, for accepting user input defining a first modification at a first enhancement point of a first source code component, the first source code component not being modified. Creating a second source code component for the first enhancement point, the second source code component being separate from the first source code component. Incorporating into the second source code component the first source code component and an expression of the first modification. And creating a compiled program using the second source code component.

Abstract: A user declarative language for formatted data processing is provided. The user declarative language may be used to generate constraints which can be projected onto a string according to one or more anchor points. The constraints can correspond to evaluation criteria. At least a portion of a string can be evaluated according to the evaluation criteria.

Abstract: A system/method for profiling a sequence of values from a range to determine a frequency of occurrence of a subrange includes, for a current block, determining whether cells of the current block include a count cell or a pointer cell. If the cell includes a pointer cell, follow an address that the pointer makes reference to and designate a new block as the current block and repeat the determining step for the new block. If the cell includes a count cell, increment the count cell and compare the incremented count cell to a threshold. If the count exceeds the threshold, convert the count cell to a pointer cell, which points to a newly allocated block. The newly allocated block is made the current block, and the steps are repeated until count cells do not exceed the threshold or a limit resolution is achieved.

Abstract: Compiled configuration files for different programmable logic devices that are intended to be functionally equivalent may be compared using multiple different comparisons to assure functional equivalence. The different comparisons include a fitter or resource report comparison, an engineering bit settings report that compares vectors of bits that represent the settings of hard logic blocks, and comparisons based on location, connectivity and functionality. These comparisons are particularly well-suited for determining equivalence between different models of programmable logic devices, or even different types of devices such as field-programmable gate arrays as compared to mask-programmable logic devices.

Abstract: Techniques for efficiently isolating software regressions are provided. A system test tool determines that a particular regression is present in a particular build of a software system, but not in a baseline build. Using historical data, the tool determines, for each of a plurality of intermediate builds between these two builds, a likelihood that that intermediate build introduced the particular regression. A particular intermediate build can be identified as a build to be tested. Here, the particular intermediate build comprises a plurality of layered putbacks, each of which putbacks comprises one or more code changes in the software system. The tool determines, for each putback, a likelihood that that putback introduced the particular regression. A particular putback in the plurality of putbacks may be selected as a putback to be tested. In some embodiments, the particular putback is the putback that has the greatest likelihood of introducing the particular regression.

Abstract: Methods, apparatus, and articles of manufacture to perform runtime trace filtering associated with application performance analysis are disclosed. A disclosed example method involves generating a first performance value based on first performance data associated with a first function of a first application process. A difference value is generated based on the first performance value and a historical performance value associated with the first function. The difference value is compared to a threshold value, and first trace data associated with execution of the first application process is collected based on the comparison of the difference value to the threshold value.

Abstract: A “kill” intrinsic that may be used in programs for designating specific data objects as having been “killed” by a preceding action is provided. The concept of a data object being “killed” is that the compiler is informed that no operations (e.g., loads and stores) on that data object, or its aliases, can be moved across the point in the program flow where the data object is designated as having been “killed.” The “kill” intrinsic limits the reordering capability of an optimization scheduler of a compiler with regard to operations performed on “killed” data objects. The “kill” intrinsic may be used with direct memory access (DMA) operations. Data objects being DMA'ed from a local store of a processor may be “killed” through use of the “kill” intrinsic prior to submitting the DMA request. Data objects being DMA'ed to the local store of the processor may be “killed” after verifying the transfer completes.

Abstract: A system for modifying a rule base for use in processing data, wherein an instance of an entity comprises associated data, for use with a parser for identifying a first instance of an entity in data associated with a document set in accordance with a first rule and for using the first instance of the entity to identify a second instance of the entity in the data associated with the document set. The system comprises an accessor for accessing data associated with the second instance of the entity; and a generator for using the data associated with the second instance of the entity to generate a second rule.

Abstract: A facility for debugging in an operating system with native and non-native subsystems is described. The facility employs a debugger designed for use with the native subsystem. The debugger receives an indication to debug the application program of the non-native subsystem, attaches to the application program of the non-native subsystem, and when it receives an indication that the application program has started a new process, attaches to an executable component operating in the new process. When the debugger is appropriately configured, the facility attaches to an application program operating on the non-native subsystem rather than a terminal component operating on the native subsystem. When the debugger is appropriately configured, the facility redirects exceptions the debugger receives to the non-native subsystem.

Abstract: A patch-based mechanism is disclosed for providing fast invocations of a target method from a compiled calling method. The code for the calling method is stored into a storage. The code for the calling method comprises an instruction for invoking the target method, where the instruction comprises a parameter. In response to a state change from a current state to a new state that is experienced by the target method, the parameter is modified from a first value to a second value, where the second value indicates the correct address for facilitating the execution of the target method in its new state. Thus, the parameter in the instruction for invoking the target method always reflects the correct state of the target method, which provides for a fast invocation of the target method when the instruction is executed.

Abstract: A meta object facility file is parsed into a plurality of schema elements. For each schema element, it is determined that the definition of the schema element is complete. A computing artifact usable in a database description language database table or a JAVA class is created from the schema element. When the schema element is a meta object facility class, a modeling entity is created to store the computing artifacts derived from the meta object facility file wherein the modeling entity is a JAVA class. The meta object facility class is transformed into a JAVA class, and upon determining that an attribute of the meta object facility class has an array of values, an array table is created and identified in the modeling entity, and an array attribute is added to JAVABEAN information in the modeling entity.

Abstract: A method of detecting recursive instantiation loops in a wireless application. A data model digraph is constructed including a respective node for each data component in the wireless application, and a respective edge for each relationship between a pair of data components. The data model digraph is searched to identify any cycles. For each identified cycle, each data component that participates in the cycle is identified.

Abstract: A system and method for advanced polyhedral loop transformations of source code in a compiler are provided. The mechanisms of the illustrative embodiments address the weaknesses of the known polyhedral loop transformation based approaches by providing mechanisms for performing code generation transformations on individual statement instances in an intermediate representation generated by the polyhedral loop transformation optimization of the source code. These code generation transformations have the important property that they do not change program order of the statements in the intermediate representation. This property allows the result of the code generation transformations to be provided back to the polyhedral loop transformation mechanisms in a program statement view, via a new re-entrance path of the illustrative embodiments, for additional optimization.

Abstract: A computer-implemented method may include receiving first data that includes one or more configuration parameters that characterize an intended deployment of software and a target computer system on which the software is to be deployed. The computer-implemented method may further include calculating a deployment risk level based on the first data, determining whether the calculated deployment risk level is less than a threshold risk level, and transmitting second data to target computer system authorizing deployment of the software if the deployment risk level is less than the threshold risk level. In some implementations, the software is enterprise software. The one or more configuration parameters may include hardware specifications of the target computer system, and the calculated deployment risk level may be based on threshold recommended hardware specifications of the target computer for running the software to be deployed.