Service Manuals, User Guides, Schematic Diagrams or docs for : xerox sdd memos_1981 Collecting_and_Analyzing_Pair_Frequency_Data_for_Mesa_Opcodes_May81

<< Back | Home

Most service manuals and schematics are PDF files, so You will need Adobre Acrobat Reader to view : Acrobat Download Some of the files are DjVu format. Readers and resources available here : DjVu Resources
For the compressed files, most common are zip and rar. Please, extract files with Your favorite compression software ( WinZip, WinRAR ... ) before viewing. If a document has multiple parts, You should download all, before extracting.
Good luck. Repair on Your own risk. Make sure You know what You are doing.



Image preview - the first page of the document



>> Download Collecting_and_Analyzing_Pair_Frequency_Data_for_Mesa_Opcodes_May81 documenatation <<

Text preview - extract from the document

                Inter-Office Memorandum
  To            dragon interest                               Date            May 12. 1981

      From      Gene McDaniel                                 Location        Palo Alto

  Subject       Collecting and AnalY7jng                      Organization   csl
                Pair Frequency Data for Mesa Opcodes


ROX
      Filed on: [ivy] or . There is a
command tile, selUpFori>airs.cm on [ivy] that will fetch all the program modules the
investigator will need. The author conducted two experiments whose results may be found on ivy:

        [ivy]pairs>compiler.press, compiler.counts
        [ivy]pairs>static.press, static.counts

     The .press files are the standard output produced by the PairFreq program, and the .counts
tiles contain the raw data for experiments. The "compiler" files are the analysis and data files
associated with a run of the mesa compiler. Pair-counting was turned off while disk 10 was
performed. The static files are the analysis .and data files associated with a run of the "static"
program written by Baskett. Pair-counting was turned-off when disk 10 was likely to be performed,
however, some disk )0 probably was measured. Static makes use of the extra memory available on
a 0* machine and performs a lot of floating point arithmetic.

    Section 5 describes the interactive commands of PairFreq. The reader can usc them to read
one of the .counts files with PairFreq and then to perform further analysis.

2.   A Simple Scenario
     Suppose you have a program for which you wish to collect dynamic pair frequency
information. Proceed with the following steps:

        1.   Find aIM-word Dorado.
        2.   Move your program to that Dorado
        3.   Fetch [ivy]setUpForPairs.cm
        4.   Type "@setUpForPairs.cm"(carriage return)
        5.   Run you program
        6.   Type "StopM icroPcPairs (carriage return)"
        7.   Type "PairFreq (carriage return)"
        8.   Print Mesa.typescript to see the standard analysis.

3.   About Data Collection
     The author modified the Mesa microcode to provide for gathering instruction pair data. There
is a "miscellaneous" instruction whose parameter is a LONG POINTER to an array of 2t16 LONG
CARDINALS! This array is named "pairData". When the pointer is 0, the microcode does not
collect pair frequency data. The microcode entry point for most instructions has been modified so
that it contains a subroutine call to the pair frequency collector. The pair frequency collector
increments the LONG. CARDINAL whose index is indicated by the concatenation of the last
opcode with the current opcode. To provide a better gauge for true PRINe OPS and Dragon
behavior, the microcode ignores no-op instructions. The effect is as if the sequence  were really .       This has been done because the Alto/Mesa
implementation has an unnatural number of no-ops. An instruction that has not been instrumented
will be counted as if it were instruction 377B.

     Ease of microcode implementation requires 

◦ Jabse Service Manual Search 2024 ◦ Jabse Pravopis ◦ onTap.bg ◦ Other service manual resources online : Fixya ◦ eServiceinfo