Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Chris Townley Newsgroups: comp.os.vms Subject: Re: New VSI blog post Date: Thu, 1 Aug 2024 12:50:43 +0100 Organization: A noiseless patient Spider Lines: 81 Message-ID: References: <6a4abd66ad3ca9bb0a026dc8ae674d187cb71efe@i2pn2.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Thu, 01 Aug 2024 13:50:44 +0200 (CEST) Injection-Info: dont-email.me; posting-host="0f3b837081ad3e7d419dc0f1b6e0d8b2"; logging-data="2259841"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+gcA9UCPivxavea+cXI5VnzQVCKbpdri0=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:U40kAzCVAkpG4khwt4uwA8+X59A= In-Reply-To: <6a4abd66ad3ca9bb0a026dc8ae674d187cb71efe@i2pn2.org> Content-Language: en-GB Bytes: 4492 On 01/08/2024 03:01, John Reagan wrote: > On 7/31/2024 6:54 PM, Chris Townley wrote: >> On 31/07/2024 21:50, John Reagan wrote: >>> On 7/30/2024 6:21 PM, Richard Jordan wrote: >>>> On 7/29/24 6:44 PM, Arne Vajhøj wrote: >>>>> For those that have not seen it: >>>>> >>>>> https://vmssoftware.com/resources/blog/2024-07-26-rtl8/ >>>>> >>>>> (Darya is listed as author, John Reagan is quoted in it) >>>>> >>>>> Content is a rather unusual mix of: >>>>> * some business/admin stuff >>>>>      - 8.4-2L1 going out of standard support in December >>>>>        so time to update to 8.4-2L3 >>>>>      - a warning about known issues in C RTL 8 and a suggestion >>>>>        to wait for C RTL 9 >>>>> * some programming notes about problems related to: >>>>>      - use of uninitialized variables >>>>>      - mismatch between 32 and 64 bit >>>>> >>>>> Arne >>>>> >>>>> >>>> Just to request clarification... are the C RTL issues across all >>>> platforms or just x86 specific?  The blog post mentioned the legacy >>>> GEM compiler "would" (past tense) pad the space and the LLVM does not. >>>> >>>> We're not getting LLVM behavior on the older systems, are we?  Alpha >>>> and Integrity behavior will remain the same? >>>> >>>> I ask because we no longer have access to a C compiler; connecting >>>> code was built to interface BASIC to FreeTDS, GSOAP and other >>>> packages long ago when we had the HP developer licenses which are >>>> long gone.  I only have access to BASIC (which is the primary >>>> language) and really don't want to try to rewrite the connector code >>>> if it turns out to have problems on an upgraded test system. >>>> >>>> And also don't want to find out we have issues with any packages >>>> that VSI may no longer be supporting (like GSOAP?) >>>> >>>> Thanks >>> Most of our CRTL changes have been for all targets.  For >>> Alpha/Itanium, the delivery method is with ECO kits.  For x86, >>> simplying upgrading the OS from V9.2 to V9.2-1 to V9.2-2 etc. will >>> pick up the new features. >>> >>> The LLVM code generator is only for x86 targets.  There are no >>> currently active LLVM targets for Alpha or Itanium.  There would be >>> no benefit to a switch, only lots of risk.  We haven't upgraded the >>> Alpha/Itanium compilers in a long time.  The only one with an active >>> bug we need to fix is with the /SEPARATE qualifier with Fortran and >>> BASIC on Itanium (it is also broken for a different reason on x86) >>> >>> The x86 BASIC compiler is finished and will be available on the >>> portal in the next day or so (for those who have access) >>> >>> $ show sys/noproc >>> OpenVMS V9.2-2  on node X86VMS   31-JUL-2024 16:48:23.70   Uptime  7 >>> 03:53:46 >>> $ basic/version >>> VSI BASIC x86-64 V1.9-001 (GEM 50Y7I) on OpenVMS x86_64 V9.2-2 >>> >>> $ show sys/noproc >>> OpenVMS E9.2-3  on node X86VMS   31-JUL-2024 16:48:32.66   Uptime  14 >>> 03:18:17 >>> $ basic/version >>> VSI BASIC x86-64 V1.9-001 (GEM 50Y7I) on OpenVMS x86_64 E9.2-3 >>> >> >> Do we need 9.2-3, or is 9.2-2 enough? >> I do know I need to recompile everything >> > V9.2-2 is sufficient. Thanks -- Chris