Sujet : Re: New VSI blog post
De : craigberry (at) *nospam* nospam.mac.com (Craig A. Berry)
Groupes : comp.os.vmsDate : 30. Jul 2024, 23:46:16
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v8bqfo$16r8v$1@dont-email.me>
References : 1 2
User-Agent : Mozilla Thunderbird
On 7/30/24 5: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?)
As far as I can see, there is no "RTL v8" kit for x86, only Alpha and
Itanium. So I infer the RTL v8 kit is a bridge to get the CRTL (and
maybe other RTLs) on Alpha and Itanium up to where it is on OpenVMS x86
9.2-2. If there is an RTL kit for x86 before 9.2-3, I don't think it
would be "v8." But this is just me making inferences based on how I
think it works.
On your C compiler problem, have you priced a single-user license on one
node just to be able to build stuff?