[Info-vax] C99 stuff (Re: The Road to V9.0)

[Stephen Hoffman]

On 2019-06-09 21:01:25 +0000, Craig A. Berry said:

> On 6/9/19 10:30 AM, John Reagan wrote:
> 
>> You won't need any of our changes to clang/clang++ if you are just 
>> interested in porting over open source code. No open source code has 
>> OpenVMS'isms buried in it. However, if you want RTL name prefixing, 
>> etc., you'll need our edits. Since we will be providing a full 
>> clang/clang++, getting it from VSI will be the easy way. Nobody here 
>> wanting to hack new stuff into clang?
> 
> I wouldn't think so....

LLVM and the clang bits are modular, which means the potential for 
integrating into IDEs and editors.

Or LLVM as a back-end for another language.

Or as part of converting source code.

Or just getting ClangFormat installed and working, if that's not in the 
stock VSI package.

Etc.

>> By the way, Rust is written in Rust, not C++. You have to bootstrap 
>> from another platform. [I've spoken to Niko in person.]
> 
> Good to know.

Rust for the parser and run-time and tooling certainly, and a whole lot 
of C++ for the LLVM back-end, when last I checked.

For the initial port and initial compiler bootstrap, I'd look at a 
couple of different approaches.

...At compiling to object or maybe to IR and then transferring that to 
the target environment and then try linking that.

...At trying to get the LLVM C back-end mostly-working, then 
transferring that and building that.
https://github.com/draperlaboratory/llvm-cbe

There may well be other good approaches here, too.

Goal is to get enough of this hackery working to get the compiler 
running native.  Not a complete cross-compiler.



-- 
Pure Personal Opinion | HoffmanLabs LLC