This is the mail archive of the
mailing list for the Cygwin project.
- From: Reini Urban <rurban at x-ray dot at>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 19 Feb 2015 20:46:27 +0100
- Subject: Re: ffcall
- Authentication-results: sourceware.org; auth=none
- References: <54E4DEC2 dot 2060400 at cornell dot edu> <1424287689 dot 3460 dot 19 dot camel at cygwin dot com> <20150218200825 dot GB22849 at calimero dot vinschen dot de> <54E51500 dot 8070200 at cornell dot edu> <20150219093852 dot GA4783 at calimero dot vinschen dot de> <54E6048C dot 6060605 at x-ray dot at> <54E61348 dot 9080104 at cornell dot edu> <54E61B05 dot 2050109 at cornell dot edu>
On 02/19/2015 06:19 PM, Ken Brown wrote:
> On 2/19/2015 11:46 AM, Ken Brown wrote:
>> On 2/19/2015 10:43 AM, Reini Urban wrote:
>>> 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:
>>>> 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
>>>>> 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.
>> Yes, it seems to be. So far I've built and am testing a version with no
>> non-default modules, and with the default regexp module disabled. I had
>> to do the latter because of the gcc problem I encountered while trying
>> to compile regexi.c:
>> The same sort of error occurs with several other modules.
Huh, that's a good one! Something for Kai.
> I tried to test my build by using it to build xindy. It appeared to
work, as far as it went, but it didn't go too far because xindy requires
the regexp module. So I think I'm stuck until the gcc problem is resolved.
> I don't whether it's worth uploading my crippled clisp at this point
> to let it get some testing. Reini, is clisp without regexp at all
Usually clisp users don't need the regexp module, they usually have
But xindy needs it, so... :)
And the deal with the latest clisp 2.49 was that modules can be dynaloaded.
If the gnulib steps would work. I never did for me. And I fixed most of
module compilation problems before.