[Info-vax] VMS84*_UPDATE

[VAXman- at SendSpamHere.ORG]

In article <4d66df5e$1 at news.langstoeger.at>, peter at langstoeger.at (Peter 'EPLAN' LANGSTOeGER) writes:
>{...snip...}
>
>but these ones are (VMS84I_UPDATE-V0500.RELEASE_NOTES)
>
>        5.2.3   The MOVAQ instruction fails to handle negative numbers
>
>                5.2.3.1  Problem Description:
>
>                The MOVAQ instruction cannot handle negative integers specified
>                in decimal format. The MOVAQ instruction considers negative
>                integers as large positive integers.
>
>                For example,
>
>                $ type movaq.mar
>                    neg = -8
>                    xneg = ^xfffffff8
>                   .psect  data,rd,wrt
>                z: .blkl   10
>
>                   .psect  code,rd,nowrt
>                   .entry  start,0
>
>                    MOVAQ xneg+z,r16
>                    MOVAQ neg+z,r18
>                    ret
>                    .end start
>
>                The MOVAQ instruction treats '-8' as a large 64-bit constant
>                value, though it handles ^xfffffff8 correctly.
>
>                This problem has been fixed.
>
>                Images Affected:
>
>                - [SYSEXE]MACRO.EXE
>
>                Quix cases reporting this problem:
>
>                None.
>
>                5.2.3.2  Work-arounds:
>
>                None.
>
>
>        5.2.4   MACRO compiler generates incorrect debugging information
>
>                5.2.4.1  Problem Description:
>
>                MACRO compiler generates incorrect debugging information for
>                certain variables. When you try to access these variables,
>                the debugger displays an error message.
>
>                This problem has been fixed.
>
>                Images Affected:
>
>                - [SYSEXE]MACRO.EXE
>
>                Quix cases reporting this problem:
>
>                None.
>
>                5.2.4.2  Work-arounds:
>
>                None.
>
>
>        5.2.5   MACRO INDEX instruction incorrectly generates a trap
>
>                5.2.5.1  Problem Description:
>
>                The MACRO INDEX instruction incorrectly generates a trap
>                when the application code uses the same register as both
>                input and output register.
>
>                This problem has been fixed.
>
>                Images Affected:
>
>                - [SYSEXE]MACRO.EXE
>
>                Quix cases reporting this problem:
>
>                QXCM1000976996
>
>                5.2.5.2  Work-arounds:
>
>                None.
>
>
>      o  [SYSEXE]MACRO.EXE (new image)
>
>         Image Identification Information
>
>         Image name: "MACRO"
>         image file identification:  "50-120-5-50F9M"
>         image file build identification:  "0100000003"
>         linker identification:  "Linker I02-37"
>         Link Date/Time: 11-OCT-2010 15:18:05.08
>         Overall Image Checksum: E70FCB13
>
>But you do checked it yourself already, didn't you?

Ah, that was JUST released (2011/02/23).  The debug bug and the INDEX bug
are reported fixed!  :)

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.