public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Reini Urban <rurban@x-ray.at>
To: cygwin-apps@cygwin.com
Subject: Re: ffcall
Date: Thu, 19 Feb 2015 15:43:00 -0000	[thread overview]
Message-ID: <54E6048C.6060605@x-ray.at> (raw)
In-Reply-To: <20150219093852.GA4783@calimero.vinschen.de>

On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
> On Feb 18 17:41, Ken Brown wrote:
> Help with basic x86_64 assembler is ok, I did it for Cygwin with help
> from Kai Tietz.
>
> The main difference to Linux you have to look out for is the different
> calling convention and how the registers are used:
> http://en.wikipedia.org/wiki/X86_calling_conventions#Microsoft_x64_calling_convention
>
> So the job is typically to rearrange the register usage and to
> account for the only four registers used for the first arguments
> to a function, rather than the 6 registers in the SYSV ABI.
>> I might give it a try at some point, but I'm not highly motivated unless
>> someone who really cares about clisp steps forward to help.  I'll
>> concentrate first on seeing if I can get some 64-bit version of clisp built
>> without ffcall.
Should be doable without. In the meantime I started here:
https://github.com/rurban/ffcall/tree/win64 with a win64 port, time permits.

win64 also needs 32byte shadow stack space to spill rcx, rdx, r8 and r9.
libffi added win64 and cygwin64 support recently, but ffcall is easier to
understand, and faster.

  reply	other threads:[~2015-02-19 15:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 18:49 ffcall Ken Brown
2015-02-18 19:28 ` ffcall Yaakov Selkowitz
2015-02-18 20:08   ` ffcall Corinna Vinschen
2015-02-18 22:41     ` ffcall Ken Brown
2015-02-19  9:38       ` ffcall Corinna Vinschen
2015-02-19 15:43         ` Reini Urban [this message]
2015-02-19 16:45           ` ffcall Ken Brown
2015-02-19 17:18             ` ffcall Ken Brown
2015-02-19 17:44               ` ffcall Corinna Vinschen
2015-02-19 18:47                 ` ffcall Ken Brown
2015-02-19 19:46               ` ffcall Reini Urban
2015-02-19 22:30                 ` ffcall Ken Brown
2015-02-21 10:03                   ` ffcall David Billinghurst
2015-02-21 17:16                     ` ffcall Ken Brown
2015-02-21 20:43                     ` ffcall Achim Gratz
2015-02-21 21:04                       ` ffcall Achim Gratz
2015-02-23 11:38                         ` ffcall Corinna Vinschen
2015-02-23 17:48                           ` ffcall Achim Gratz
2015-02-23 20:32                             ` ffcall Corinna Vinschen
2015-02-23 20:56                               ` ffcall Achim Gratz
2015-02-21  3:45                 ` ffcall Ken Brown
2015-02-21 12:59                   ` ffcall Reini Urban
2015-02-21 17:20                     ` ffcall Ken Brown
2015-02-18 22:17   ` ffcall Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54E6048C.6060605@x-ray.at \
    --to=rurban@x-ray.at \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).