Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Retrofix: Creating Fix Control Statements for Monolithic Program Objects

IP.com Disclosure Number: IPCOM000111708D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 72K

Publishing Venue

IBM

Related People

Cayce, J: AUTHOR [+5]

Abstract

This article describes a "retrofix tool" whose purpose is to allow microcoders to make source level changes to component modules of a microcode link orto add new modules to the link without needing to re-translate the modules of the entire link.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Retrofix: Creating Fix Control Statements for Monolithic Program
Objects

      This article describes a "retrofix tool" whose purpose is to
allow microcoders to make source level changes to component modules
of a microcode link orto add new modules to the link without needing
to re-translate the modules of the entire link.

      While retrofix allows the alteration of a link at the source
level, it operates almost exclusively using the translated object
(MOBJ) of both the link as originated and of the module(s) being
changed.  The set of changes resulting from a retrofix run is called
a "fix".

      Fixes are sets of changes to the link microcode image which
when overlaid on the link produce a microcode image equivalent to
that which would have been produced if the source code changes which
produced the fix had been originally incorporated in the link.  This
set of changes is typically used on hardware simulation, but can also
be used to produce an actual microcode image for use on hardware.

The production of a fix comrprises the following steps:

1.  Object code and expanded source acquisition for all source code
    modules involved in the fix.

2.  Construction from the object modules of a list of all symbols and
    a list of all module displacement addresses and microwords for
    all modules involved in the fix.

3.  Verification of symbol use safety.  Duplication, elimination and
    unresolved references of symbols are detected and errors reported
    to the user.  Additionally, dependencies on symbols which are
    themselves in a state of change by being involved in an
    unpromoted fix are detected and errors generated.

4.  Space checking of all modules either to verify that they do not
    exceed their present space allocation or to detect an oversize
    condition and find free space for relocation of the module(s)
    within the link.

5.  The generation of...