OpenCores
URL https://opencores.org/ocsvn/i650/i650/trunk

Subversion Repositories i650

[/] [i650/] [trunk/] [utils/] [ibm650_soap2/] [ibm650_soap2/] [recreating_soap2.rtf] - Blame information for rev 29

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 29 eightycc
{\rtf1\ansi\ansicpg1252\cocoartf1347\cocoasubrtf570
2
\cocoascreenfonts1{\fonttbl\f0\fnil\fcharset0 LucidaSans;\f1\fnil\fcharset0 LucidaBright;}
3
{\colortbl;\red255\green255\blue255;}
4
\margl1440\margr1440\vieww9000\viewh8400\viewkind0
5
\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural
6
 
7
\f0\fs28 \cf0 Recreating SOAP 2 Source and Object\
8
 
9
\f1\fs24 \
10
From IBM publication 32-7646-1 "SOAP II for the IBM 650 Data Processing System"[1], I hand entered both the source statements and the 7-word object deck. \
11
\
12
Next, I verified the 7-word object deck by comparing a reading by voice synthesis with the original. I improved the audibility of the reading by first running the object deck through a small utility that added punctuation.\
13
\
14
I then wrote a program equivalent to SOAP 2 in C++ that included a command line switch to compare the generated object code with a 7-word object deck.\
15
\
16
Because SOAP 2 allocates operand and instruction locations according to an optimization algorithm, both the generated object code and its assigned location must be correct. This required that the optimization algorithm in my C++ code match the original in SOAP 2 exactly.\
17
\
18
Running the SOAP 2 source through my C++ code did not produce matching object code. Surely there were typos, but eliminating them did not improve object. The optimization algorithm in my code appeared to be working correctly. \
19
\
20
The problem turned out to be that some statements in the published listing were presented out of order. This may be the result of the author arranging the statements prior to assembly for optimal placement, and rearranging them for clarity. This reordering occurs in the main processing loop, symbol table lookup, and optimum location lookup and reservation.\
21
\
22
Another problem resulted from a patch made to the optimization table entries for the MPY and DIV instructions. It appears that the distributed SOAP 2 was assembled with a version of SOAP 2 that reversed the odd/even I optimization constants. The SOAP 2 listing and 7-word deck are corrected in [1].\
23
\
24
\
25
   }

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.