OpenVMS ALPAMAC02_070 Alpha V7.0 AMACRO ECO Summary

 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 
*OpenVMS] ALPAMAC02_070 Alpha V7.0 AMACRO ECO Summary
 
Copyright (c) Digital Equipment Corporation 1996.  All rights reserved.

PRODUCT:    OpenVMS Alpha 

COMPONENT:  ALPHA_MACRO.EXE - AMACRO 

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  ALPAMAC02_070
     ECO Kits Superseded by This ECO Kit:  ALPAMAC01_070
     ECO Kit Approximate Size:  10710 Blocks

     Kit Applies To:  OpenVMS Alpha V7.0
     System/Cluster Reboot Necessary:  Yes

     Installation Rating:   3 - To be installed on all systems running
                                the listed versions of OpenVMS which
                                are experiencing the problems described.

     NOTE:  In order to receive the full fixes listed in this kit,
            the following remedial kits also need to be installed:

                 None.  


ECO KIT SUMMARY:

An ECO kit exists for ALPHA_MACRO.EXE on OpenVMS Alpha V7.0.
This kit addresses the following problems: 

Problems addressed in ALPAMAC02_070:

  o  MACRO source code containing INSV instructions can access
     violate when the value of the position operand goes negative.
     This will correct the generated code so that the operation is
     the same as on OpenVMS VAX.  EXTZV and EXTV generation are 
     similarly afflicted.

  o  Code containing two arithmetic, logical, or bitwise byte/word
     operands causes the compiler to access violate.  Even if an
     access violation did not occur, the current flow of control 
     in the code generator would cause the compiler to generate 
     inappropriate load-locked store-conditional sequences.  This 
     behavior is governed by the use of /preserve=(atomicity) or 
     /preserve=(granularity).



  o  AMACRO is destroying one of the argument registers on a call when        
     temporary registers are in short supply.                                 


INSTALLATION NOTES:

In order for the corrections in this kit to take effect, the system
must be rebooted.  If the system is a member of a VMScluster, the 
entire cluster should be rebooted. 

Colorado Site
Georgia Site

alpamac02_070.README
alpamac02_070.CHKSUM
alpamac02_070.CVRLET_TXT
alpamac02_070.a-dcx_axpexe