PAWS
Release Notes - Miscellaneous, 8/13/98
Table of Contents
1.0 Overview
1.1 Enhancements
1.1.1 ATLAS Program Retargetter
1.2 Problem Reports
2.0 Detailed Description
2.1 Enhancements
2.1.1 Targetter - Execution on MS-DOS 16-Bit and 32-Bit Systems.
2.2 Problem Reports
1.0 Overview
This document describes changes included within:
|
Module Name
|
Module Description
|
|
Targetter
|
Atlas Program Retargetter
|
|
Module
|
Changes
|
Rebuilt
|
Current Version
|
|
Targetter
|
Major
|
Yes
|
19980813 3.8.2
|
1.1 Enhancements
1.1.1 ATLAS Program Retargetter
Available for execution on MS-DOS 16-Bit and 32-bit Systems.
1.2 Problem Reports
Corrections for the following Problem Reports were incorporated in this Release:
PR 98-055 Targetter Fails to correctly re-target any "linked" and "allocated" ATLAS Test Program for which the Resource Allocator has inserted Device Database Macro Code.
2.0 Detailed Description
2.1 Enhancements
2.1.1 Targetter - Execution on MS-DOS 16-Bit and 32-Bit Systems.
Prior to this release, the Targetter was available for execution only on UNIX Systems.
With this release, the Targetter is available for execution on both UNIX Systems and MS-DOS 16-Bit and 32-Bit Systems. The MS-DOS Targetter consists of the following two Files:
|
\usr\tyx\bin\targeter.exe
|
Executable Program
|
|
\usr\tyx\bin\targeter.txt
|
User Information
|
2.2 Problem Reports
PR 98-055 Targetter Fails to correctly re-target any "linked" and "allocated" ATLAS Test Program for which the Resource Allocator has inserted Device Database Macro Code.
Prior to this release, the Targetter detected the end of an ATLAS Unit in the .OBJ File by comparing the Virtual Address (VA) of the next AIL to be processed with the VA of the start of the next ATLAS Unit. This accidentally worked correctly with non-linked ATLAS Programs because there is only one ATLAS Unit. However, this did not work correctly with linked ATLAS Programs containing two or more ATLAS Units and containing Device Database Macro Code generated by the Resource Allocator because the Resource Allocator generates such Code at the end of the last ATLAS Unit and then links it into the AIL Linked List at the STM AIL of the Begin ATLAS Statement (which is in the first ATLAS Unit). The Targetter would correctly process the Begin ATLAS STM AIL, see the VA of the next AIL (i.e., the first AIL generated by the Resource Allocator) was past the start of the next ATLAS Unit and, not only fail to process this AIL, but also fail to process any of the remaining AIL's in the first ATLAS Unit. Attempting RTS execution of the incorrectly processed .OBJ would give unpredictable results, the best of which was an RTS System Abort.
With this release, the Targetter terminates processing of an ATLAS Unit upon detection of an STM AIL with a VA greater than the VA of the start of the next ATLAS Unit.
This Problem Report has been closed.
|