Abstract: Client-side and server-side methods and systems for the automatic storage of contact information on a cellular phone are disclosed. Contact information is received from a directory assistance service, and stored in the memory of a cellular phone. The contact information may be placed in memory associated with a contact list (phonebook), memory associated with recently dialed calls, or both. A redial function may also leverage the contact information. When new information is received relating to an existing contact, the existing contact information may be replaced by, or updated with, the new contact information. Alternatively, an additional entry can be added for the contact information, and the existing contact retained.

Abstract: Systems, methodologies, media, and other embodiments associated with an object-oriented interface to register transfer language (RTL) signals are described. One exemplary system embodiment includes logic for acquiring the address of an RTL signal and for providing method level access to the RTL signal. The exemplary system embodiment may also include an object that facilitates establishing a relationship between the RTL signal address and RTL signal name and thus facilitates providing method level access to the RTL signal.

Abstract: Systems, methodologies, media, and other embodiments associated with manipulating model specific registers are described. One exemplary system embodiment includes a model specific register logic that facilitates manipulating a model specific register so that bits that are irrelevant to a processor simulation are not set for the processor simulation. The exemplary system may also include a data store that is configured to store significance vectors that encode information about (ir)relevant model specific register bits and that facilitate the model specific register logic manipulating a model specific register to a desired initial state.

Abstract: One exemplary system embodiment includes a detection logic that facilitates identifying that a point-to-point transaction is a transaction that is not micro-architecturally implemented and a tracking logic that facilitates tracking the transaction and related packets through the virtual bus interface and that also facilitates producing an error data associated with the non-micro-architecturally implemented transaction.

Abstract: Systems, methods and software products are provided for transaction logging and intelligent error reporting in an expectation-based memory agent checker. Simulation status information is appended to one or more transaction log messages generated by the expectation-based memory agent checker. A cause of error indicated by mismatch between simulated output transaction events and expected output transaction events is determined. Information about the error is appended to one or more error messages generated by the expectation-based memory agent checker.

Abstract: Systems, methodologies, media, and other embodiments associated with detecting a cache coherency protocol mode associated with a system that provided a point-to-point transaction to a virtual bus interface are described. One exemplary system embodiment includes a detection logic that facilitates identifying the cache coherency protocol mode. The exemplary system embodiment may also include a coding logic that facilitates selectively processing packets associated with a point-to-point transaction into a bus model transaction, where the packet processing depends, at least in part, on the cache coherency protocol mode.

Abstract: Systems, methodologies, media, and other embodiments associated with a system for producing a bus-type header-type field from a point-to-point data-type field are described. One exemplary system embodiment includes a logic configured to identify that a point-to-point transaction includes non-memory-data information encoded in a data flit, a logic configured to extract the non-memory-data information from the data flit, and a logic configured to produce a header-type field for a bus-type transaction produced by the virtual bus interface from the point-to-point transaction.

Abstract: Systems, methodologies, media, and other embodiments associated with processing point-to-point transactions that are not be processed into bus model transactions by a virtual bus interface configured to convert point-to-point transactions into bus-type transactions are described. One exemplary system embodiment includes a detection logic that facilitates identifying that a point-to-point transaction is a transaction type that is not be processed into a bus model transaction and a tracking logic that facilitates tracking the transaction and related packets through the virtual bus interface and that also facilitates suppressing generating a bus model transaction from a point-to-point transaction.

Abstract: Systems, methods and software products are provided for error tracking and recovery in an expectation-based memory agent checker. An electronic device design is simulated with stimuli of one or more test cases, to generate simulated output transaction events. The simulated output transaction events are compared with expected output transaction events. Remaining expected output transaction events for a transaction are identified based upon mismatch between (a) at least one of the simulated output transaction events of the transaction and (b) the expected output transaction events of the transaction.

Abstract: Systems, methods and software products are provided for lockstep mode test case initialization of a multi-core processor. One or more initialization statements of the test case simulation are determined that identify one or more first registers of a simulated primary core. If the test case simulation specifies that the multi-core processor design operates in lockstep mode, scope of the initialization statements is modified. The first registers specified by the initialization statements are initialized, and unmodified initialization statements are processed to initialize second registers of simulated cores of the multi-core processor design, as specified by the unmodified initialization statements.

Abstract: Disclosed are systems and method for identifying similar bugs. In one embodiment, a system and a method pertain to generating a database that contains database tokens that relate to identified bugs, generating input tokens associated with a bug in question, scanning the database for occurrences of the input tokens, and determining an overall probability as to whether the identified bugs are the same as the bug in question.

Abstract: Disclosed are systems and methods for determining bug ownership. In one embodiment, a system and a method pertain to generating a database that contains database tokens that relate to identified bugs and that are associated with potential owners, generating input tokens associated with a bug in question, scanning the database for occurrences of the input tokens, and determining an overall probability of ownership of the bug in question for potential owners in the database.

Abstract: Disclosed are systems and methods for identifying unending transactions. In one embodiment, a system and a method pertain to monitoring an interface, determining whether a transaction has timed out, and flagging the transaction if it is determined that the transaction has timed out. In another method, a system and a method pertain to monitoring an interface, identifying a packet that arrives on the interface, determining whether the packet pertains to a transaction contained in a pending transaction list, and determining when the transaction should be completed if the transaction is not contained in the pending transaction list.

Abstract: Disclosed are systems and methods for identifying erroneous transactions. In one embodiment, a system and a method pertain to monitoring an interface, determining information related to termination of a test case, and after the test case has terminated, identifying an incomplete transaction that should have completed prior to termination of the test case.

Abstract: A system and method for generating a test case operable to test a circuit design using a plurality of threads. In one embodiment, a test code and state initialization engine, responsive to a random number sequence and a probability profile, generates test code. A distribution settings engine generates default distribution settings that specify a magnitude of at least one simulation parameter for each thread based on a default probability distribution profile. A knob-setting interface is included for optionally differentiating the default distribution settings. The optionally differentiated distribution settings are then associated with the test code in order to generate the test case that exercises a circuit design model of the circuit design.

Abstract: A system and method for building a test case operable to test a circuit design, the test case including a summary of instructions. In one embodiment, an instruction generation engine generates a set of instructions of which at least one instruction includes a temporarily uncommitted value. A first summary generation engine portion generates an interfaceable enumeration of the set of instructions wherein each of the temporarily uncommitted values is denoted by an uncommitted reference. A second summary generation engine portion resolves the respective values of the uncommitted references and generates an interfaceable listing of the uncommitted references and their the respective values. The set of instructions and the interfaceable listing of the resolved uncommitted references may be arranged to form the test case.

Abstract: A system and method for testing a circuit design using a test generator. In one embodiment, a random number generator, responsive to a seed, generates a random number sequence and an event probability generator, responsive to profile settings, generates a probability profile. The test generator, responsive to the random number sequence and the probability profile, generates a test case that includes settings indicative of the seed and the profile settings. An extraction and regeneration engine extracts the seed and the profile settings from the test case in order to reconstitute a test case designed to avoid illegal test behavior.

Abstract: Computerized methods and systems for modeling a structural frame of a building. One or more client computers and a central server are coupled to a data communications network. The central server receives a plurality of input parameters representative of design characteristics of the building frame from users via the client computers. The central server consolidates the input parameters according to a defined hierarchy among the users to resolve conflicts between two or more of the input parameters. The central server further generates a building frame model based on the consolidated input parameters to optimize construction of an actual building frame according to the model. The model assigns load values to load bearing members of the building frame based on connections between the members.