[llvm-dev] Porting LLVM to OpenVMS

Patrik Eklöf via llvm-dev llvm-dev at lists.llvm.org
Fri Jan 13 02:17:35 PST 2017

Thank you both for helpful replies ☺

Patrik Eklöf

Patrik Eklöf
Phone +46 720 514440

My LinkedIn<https://www.linkedin.com/company/energy-machines>
patrik.eklof at energymachines.com<mailto:patrik.eklof at energymachines.com>

[cid:image001.png at 01D26D8E.A13CB6A0]
Skeppsgatan 19, SE-211 11 Malmö, Sweden
www.energymachines.com<http://energymachines.com/>  |  LinkedIn<https://www.linkedin.com/company/energy-machines>

The information in this e-mail and any of its attachments is strictly confidential and intended solely for the person or organisation to whom it is addressed. Access to this email by anyone else is unauthorised. If you are not the intended recipient, you must not copy or distribute it or take action in reliance on it. If you have received this e-mail in error, please notify the sender as soon as possible. Communication via e-mail over the internet is not secure and messages may be read, manipulated or otherwise compromised by third parties. Energy Machines Sweden AB does not accept any responsibility in this eventuality.

From: mbraun at apple.com [mailto:mbraun at apple.com]
Sent: 10 January 2017 19:10
To: Patrik Eklöf <patrik.eklof at energymachines.com>
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Porting LLVM to OpenVMS

On Jan 10, 2017, at 12:41 AM, Patrik Eklöf via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:

Dear community,

My company is interested in porting LLVM to OpenVMS. To do so, we need to look at extending the AMD64 calling convention to suit the existing calling conventions available on OpenVMS.

We realize LLVM is a big and complex project and for some people who has not worked on it before, it’s going to be a big and tough job that is going to take a lot of time. Still, the job has to be done and we have to start somewhere, so any help or direction would be great.

Now, as to what we need:
-          To pass the argument count to the callee
-          Reserving registers for mapping variables directly to them

We need to look at passing the argument count (i.e. number of arguments passed) to functions in some register. One way that we have considered is to use the second byte of AL to hold the argument count. Do you think that would work well with how LLVM works today? Or is there an alternative way that you would suggest?

We also need to look at reserving registers because existing OpenVMS code relies on being able to map variables directly to registers so that multiple functions can share variables directly inside registers. We may need to reserve up to as many as 6 registers. Do you think this might work? Or will this make codegen bad? We have also considered trying to put these variables into an array and reserving a global variable to index into this array, thereby emulating this feature. Do you think this will work better?

It would be great to get some information to cut down on the area we need to concentrate on to get started. Any help or direction would be great.

I don't see a problem doing any of these (of course it will take some getting used to how all those things work in llvm). You can express storing a number in a fixed register with selection DAG CopyToReg and you can reserve registers.

Look around X86ISelLowering.cpp esp. LowerCall() and X86RegisterInfo::getReservedRegs().

- Matthias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170113/866058f4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7174 bytes
Desc: image001.png
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170113/866058f4/attachment.png>

More information about the llvm-dev mailing list