[Info-vax] OpenVMS I64 V8.4-1H1 Has Shipped

[Bill Gunshannon]

In article <mj4r5l$r2f$1 at dont-email.me>,
	Stephen Hoffman <seaohveh at hoffmanlabs.invalid> writes:
> This is a multi-part message in MIME format.
> 
> ----------------11831722731416419742
> Content-Type: text/plain; charset=iso-8859-1; format=flowed
> Content-Transfer-Encoding: 8bit
> 
> On 2015-05-15 11:56:30 +0000, clairgrant71 at gmail.com said:
> 
>> On Friday, May 15, 2015 at 2:54:23 AM UTC-4, JF Mezei wrote:
>>> 
>>> What will be the architecture code returned by F%GETSYI("ARCH") ?
>> 
>> x86_64
> 
> $ write sys$output f%getsyi("ARCH")
> %DCL-W-UNDSYM, undefined symbol - check validity and spelling
>  \F%GETSYI\
> $ write sys$output f$getsyi("ARCH")
> %DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
>  \ARCH\
> $ write sys$output f$getsyi("ARCH_NAME")
> x86_64
> $
> 
> 
> But OK.   So now we have something to start coding to.  Not that we 
> know all of the differences that we'll be coding here, beyond the 
> obvious stuff like the object and binary formats...
> 
> Did the various associated symbols make it into V8.4-1H1; the 
> SYI$K_ARCH_* stuff in $SYIDEF, et al?  (Looks like $HWDEF is 
> unmaintained or retired, too.)
> 
> A more general question will be the product name, if that's been 
> decided: OpenVMS X86_64?  OpenVMS X86?  OpenVMS X64?
 
Let's keep JF happy and call it OpenVMS 8086.       Just in case - :-)
 

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>