-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenVMS host support #78
Comments
You have an itanium box? Cool! Would you share some details on the hardware? Does cmake and a modern (c++ 17) compiler work on OpenVMS? |
@RaymiiOrg you can wait for the x86 version and they should work fine :) |
I think I've seen talks of a cmake porting project somewhere. But the current version of the HP C++ compiler doesn't even fully implement C++03, let alone anything more modern. 20 years of neglect of the platform show everywhere... |
I have an HP Integrity rx2620 with a single 1.3 GHz Intel Itanium 2 CPU, 8 GB of RAM and three SCSI hard drives. It's quite fast and runs OpenVMS fine.
The documentation to the HP C++ compiler is not clear, so I don't know - if it at least has C++11 features, the C++17 specific functions could be implemented as part of the source code. There are signs of OpenVMS support in the CMake codebase - based on what I found in the mailing lists the OpenVMS developers need it to build LLVM (the AMD64 compilers use LLVM as the backend). |
I hope the AMD64 porting effort will accelerate progress of C++ support, which they'll have to do if they want newer LLVM. |
As far as I know, they are using LLVM to do some porting. Hopefully, in the next weeks, I will have access to a 9.1 field test, and I will try something :) |
Yes, VSI bases the x86 VMS compilers on LLVM (and a GEM-to-LLVM converter, GEM being the "old" intermediate format). But currently they have to use an old LLVM version until the C++ part is up to compiling LLVM itself. John Reagan talked about it in a webinar. |
Yes, exactly, but the path is open now :) |
OpenVMS host support was removed in the beginning of AXPbox development, mostly because I didn't have any OpenVMS-capable hardware. However that has changed now, and porting the code to OpenVMS shouldn't be that hard, at least in theory that is.
The text was updated successfully, but these errors were encountered: