X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:to:date:in-reply-to
	:references:content-type:mime-version:content-transfer-encoding;
	 q=dns; s=default; b=nQ6sfRXwFEANc2NvG2LeICZHcIeWXC1rFDuca2KSOlZ
	mEgC6KviH1iJYBzUSKuvGgzzKKmwx/Lcow98ixFlxY+rRvuS3Oe+6lycIT0hef4C
	0fO+I6Pxd6GNXWuCEE5UcayUvVpYf1jTQ2xuQ940vg+YFVTftBCQSufl38KrpGyA
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:to:date:in-reply-to
	:references:content-type:mime-version:content-transfer-encoding;
	 s=default; bh=7vQDhQzygu4SmoQ2QdCelzOYf+w=; b=ItROS5f6aUYvLn8rp
	UEkbYiPYmLkooXqtHNSB5iJZjojFiaAOxFeyZAac5oZw8cuH+F/17SUJjg9gSVBO
	vAKvR+uP1OvaV+XNgxSA5qWDlAqq5wRlGYWg+6TQXKNRw1RzUbpp6kwr5yM9o3hH
	zkjM/CWZJDcqdGp6LQJoP6xRHQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Senior, corinna, Corinna, expertise
X-HELO: mx1.redhat.com
Message-ID: <db507cae25f6f4b20af039bf3931e727d9614f61.camel@redhat.com>
Subject: Re: 32 bit vs 64 bit Cygwin, followup
From: Yaakov Selkowitz <yselkowi AT redhat DOT com>
To: Sam Habiel <sam DOT habiel AT gmail DOT com>, cygwin AT cygwin DOT com
Date: Wed, 28 Nov 2018 10:00:59 -0600
In-Reply-To: <CABHT96207sag6z7LMMDiBQciu-B3o7zFoOkYLw3OOSi_S=Kckg@mail.gmail.com>
References: 	<CABHT96207sag6z7LMMDiBQciu-B3o7zFoOkYLw3OOSi_S=Kckg AT mail DOT gmail DOT com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On Mon, 2018-11-26 at 14:07 -0500, Sam Habiel wrote:
> Hello everybody,
> 
> In this message
> (https://www.sourceware.org/ml/cygwin/2018-11/msg00190.html), Corinna
> (Hi Corinna!) says:
> 
> "Don't do that.  Use 64 bit Cygwin whenever possible.  32 bit is a lost cause."
> 
> I would like to mention why I am still using 32 bit Cygwin.
> 
> I maintain a port of a database called GT.M
> (https://en.wikipedia.org/wiki/GT.M) on Cygwin. I work with Electronic
> Medical Records that run on this database. GT.M contains a large
> amount of assembly code, written to run on the x32 Linux ABI and the
> AMD x64 ABI. It's was very easy to get the x32 Linux ABI to run on
> Cygwin x32; Cygwin x64 on the other hand uses the Windows x64 ABI,
> which is very different than the AMD ABI (more detail here:
> https://eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64/).
> I don't have the expertise nor the time to rewrite a lot of assembly
> code to use the Windows x64 ABI. There are about 100 source code files
> that are in assembly.

-mabi=sysv ?

> By the way, thank you for the Async IO APIs. I needed those for newer
> versions of GT.M and was able to port it successfully to Cygwin x32.

-- 
Yaakov Selkowitz
Senior Software Engineer - Platform Enablement
Red Hat, Inc.



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple