[Info-vax] VSI C/C++ compiler for OpenVMS expired yesterday!

[Craig A. Berry]

On 9/4/23 3:11 PM, Single Stage to Orbit wrote:
> On Mon, 2023-09-04 at 12:57 -0700, John Reagan wrote:
>> On Monday, September 4, 2023 at 8:18:49 AM UTC-4, Simon Clubley
>> wrote:
>>> On 2023-09-02, John Reagan <xyzz... at gmail.com> wrote:
>>>> Again, my apologies for the ancient timebomb (long story)
>>>>
>>> It happens :-) however much it would be nice it didn't... :-)
>>>
>>> Has anyone checked to make sure there are no timebombs waiting
>>> to go off in the other products ?
>>
> 
>> C++ was the first native compiler prior to all of the LMF code (and
>> PAKs) being in place.
>> All of the other compilers and LPs rely on the termination date
>> feature of a PAK.
> 
> That makes complete sense, can't bootstrap without a working toolchain.

But C++ is not part of the toolchain, at least not that I've ever heard
of.  And I doubt if much of the C code in VMS would compile with clang
without modifications.

> What did you use as the host to build the toolchains and all the x86_64
> bits for VMS jut out of interest?

John is the expert, but anyone following the roadmaps over the last
several years knows that C++ is clang++ and the other compilers use a
GEM compatibility layer to generate LLVM IR.  And MACRO is special.

> Is OpenVMS for x86 now self hosting
> and can it build itself?

Most of the compilers started out as cross compilers running on Itanium
and as far as anything I've heard that's still what's in use for
building the OS itself. All of the native compilers that are available
are still in field test and likely to prioritize building customer code
for now.