Deutsch   English   Français   Italiano  
<vrpjdf$2r6bm$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=C3=B8j?= <arne@vajhoej.dk>
Newsgroups: comp.os.vms
Subject: Re: VSI compiler webinar
Date: Sun, 23 Mar 2025 14:20:30 -0400
Organization: A noiseless patient Spider
Lines: 48
Message-ID: <vrpjdf$2r6bm$1@dont-email.me>
References: <vrk01m$1pn8a$1@dont-email.me>
 <31202c11e7c49616ec97f1d5914f8d2803c2184b@i2pn2.org>
 <m4a4e3FoatU1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 23 Mar 2025 19:20:31 +0100 (CET)
Injection-Info: dont-email.me; posting-host="5e7824a049b93c6905cbed6fc7754d7d";
	logging-data="2988406"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19tMV7OGIKdK4B9Hr1hl+InX8lvjTPmoQ4="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:WHvQJqXFqpFqMRRL9pbs5kUMENA=
In-Reply-To: <m4a4e3FoatU1@mid.individual.net>
Content-Language: en-US
Bytes: 2564

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