[Info-vax] VMS84*_UPDATE
Peter 'EPLAN' LANGSTOeGER
peter at langstoeger.at
Thu Feb 24 15:44:46 EST 2011
In article <00AAB7BD.AC28B155 at SendSpamHere.ORG>, VAXman- @SendSpamHere.ORG writes:
>In article <929be20d-b1f1-42bb-8755-3f249badeb1b at q40g2000prh.googlegroups.com>, IanMiller <gxys at uk2.net> writes:
>>There are a couple of MACRO fixes - I thought they could be ones you
>>reported.
>
>Perhaps you're on a different ITRC patch list. I see 19 and none are for
>Macro.
Yes, as Ian already stated, the Macro fixes are in UPDATE ECO
and haven't been in separate ECOs before.
Not really a MACRO fix (VMS84I_UPDATE-V0400.RELEASE_NOTES)
5.1.3 Faster memory zeroing using IA64_STF_SPILL_F0 iMACRO
The IA64_STF_SPILL_F0 is a new iMACRO built-in that
allows faster memory zeroing by writing 16 bytes
of memory at a time. In the earlier versions, only
8 bytes could be zeroed using the EVAX_STQ built-in.
The IA64_STF_SPILL_F0 built-in provides significant
performance benefits, especially when zeroing large
areas of memory.
Format:
IA64_STF_SPILL_F0 addr, incr
where,
'addr' is the address of the 16-byte memory region
'incr' is the value by which 'addr' is incremented;
specifying 0 means no auto-increment.
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?
--
Peter "EPLAN" LANGSTÖGER
Network and OpenVMS system specialist
E-mail Peter at LANGSTOeGER.at
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist
More information about the Info-vax
mailing list