Earl Hubbell, 1999. Personal communication. 31  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of steps of the protocol. Typical values of m, c, and n based on previous work [8] are: m = 128, c = 4, and 60 n 100. To actually perform quality control of a protocol, the quality control probes de ned by Q are manufactured using the protocol onto m reserved spots on each chip of a wafer [7]. The manufacturer takes one chip from the wafer and tests it as follows: the chip is hybridized with uorescent targets complementary to the c probes, scanned, and the resulting vector of m intensity values is used to determine which step, if any, failed. The remaining chips of the wafer are ....

Earl Hubbell, 1999. Personal communication. 31

....us an execution count for each basic block in the program. We can combine these counts with static information from the uninstrumented program to get profile information either at the source level, such as procedure invocation counts, or at the instruction level, such as load and store counts [14,17]. Some events that we might want to count require inter block state. Counting pipeline or coprocessor stalls, for example, can be done with basic block counting only if any stall is guaranteed to finish before we leave the basic block. Counting branches taken or fallen through, or the ....

....the user need not recompile, and means we need not maintain instrumented versions of the libraries, as has been the usual practice, for example, in systems that support gprof [8] The need to relink is inconvenient, however, and it is interesting that another approach is possible. 4. Pixie Pixie [14,17], developed by Earl Killian of MIPS, does block counting and address tracing by modifying a fully linked executable. The executable file may even have had its symbol table removed, though the block counts are normally analyzed by tools that need to see the symbol table. This approach is much ....

Earl A. Killian. Personal communication.

....contains the relocation table and loader symbol table, which make the transformation easier. Lacking this information, pixie must postpone much address translation until the modified program is executed, because it cannot reliably distinguish text addresses from data values at transformation time [25]. This introduces runtime overhead that makes pixie an unsuitable vehicle for optimization, though it has been used for several of the instrumentation purposes that Mahler has. 20 EXPERIENCE WITH A SOFTWARE DEFINED MACHINE ARCHITECTURE 3.7.1. Instruction level instrumentation Our first ....

Earl A. Killian. Personal communication.

....us an execution count for each basic block in the program. We can combine these counts with static information from the uninstrumented program to get profile information either at the source level, such as procedure invocation counts, or at the instruction level, such as load and store counts [9,12]. Some events that we might want to count require inter block state. Counting pipeline or coprocessor stalls, for example, can be done with basic block counting only if any stall is guaranteed to finish before we leave the basic block. Counting branches taken or fallen through, or the distribution ....

....the user need not recompile, and means we need not maintain instrumented versions of the libraries, as has been the usual practice, for example, in systems that support gprof [6] The need to relink is inconvenient, however, and it is interesting that another approach is possible. 4. Pixie Pixie [9,12], developed by Earl Killian of MIPS, does block counting and address tracing by modifying a fully linked executable. The executable file may even have had its symbol table removed, though the block counts are normally analyzed by tools that need to see the symbol table. This approach is much more ....

Earl A. Killian. Personal communication.

....of steps of the protocol. Typical values of m, c, and n based on previous work [8] are m = 128, c =4,and 60 # n # 100. To actually perform qualitycontrol of a protocol, the quality control probes de ned by # are manufactured using the protocol onto m reserved spots on eachchip of a wafer [7]. The manufacturer takes one chip from the wafer and tests it as follows: the chip is hybridized with uorescent targets complementary to the c probes, scanned, and the resulting vector of m intensity values is used to determine which step, if any, failed. The remaining chips of the wafer are thus ....

Earl Hubbell, 1999. Personal communication. 31

No context found.

Earl Killian. Personal communication.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC