Re: VSI compiler webinar

Le 23/03/2025 à 19:20, Arne Vajhøj a écrit :

On 3/23/2025 6:00 AM, gcalliet wrote:

Le 21/03/2025 à 20:43, John Reagan a écrit :

I'm working on my witty remarks now.  However, given that I only have 45 minutes, I won't be able to perform my one-man show "BLISS, the musical!"
>
>

You'll have to be careful with old people. You know the Beatles song, when I'm sixty-four. For my part, I have two questions that I started asking at 64, a little less than ten years ago:
>
Could we collaborate on the Ada compiler?
When will we have access to the LLVM workshop?

 

You will have two questions:
>
Could we collaborate on the Ada compiler?
When will we have access to the LLVM workshop?
>
You will have two questions.

 I will assume any VMS specific changes to LLVM will
eventually make it back to upstream LLVM project - it
makes sense for VSI to avoid having to merge those
changes every time they take a new version.
 And as stated in another thread then I would love to
see VSI put all their open source usage in public
Github repo's.
 But VMS LLVM is rather old (if I remember correctly then it
is, because it had to be build on Itanium with VMS C++
for cross compilers).
 So I would rephrase the question as:
 can VSI say whether they want to:
   1) make VMS LLVM code available
   2) upgrade LLVM
or:
   1) upgrade LLVM
   2) make VMS LLVM code available
?
 :-)
 Arne
 

  Understood. I agree on all that you said.
I'll add motivation. LLVM is a foundation for many interesting languages or projects. These languages or projects ​​don't all have to be certified by VSI, but they can be the basis for very important open source developments.
Therefore, like any building block of an open source structure, publishing and updating modifications allows anyone who wants to use them to work, and it's up to the users of the building blocks to see how to adapt to the changes.
John will give us the details of LLVM's age. From my perspective, it seems to me that this is a characteristic and a general constraint for open source development with VMS. It certainly requires a specific programming art, but it doesn't prevent anything. What prevents it, we agree on this, is the absence of the source code.
Finally, when the future is magnificent, VSI will be able to return its transformations to the LLVM main stream. We're not there yet, but we have now a rich Open Source VMS workshop potentially available, if the door is open.
Gérard Calliet