X-Recipient: archive-cygwin@delorie.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:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=l4hPIKOMStGiVlbIFcGHowY0iFTiY
	VBwARdm6yuf19WHzFRQKLZ/SPh2pGVnVD7FLV4ApCGoe7MYuEwNDM+70fJt1y/iH
	6R6jg9vgTfvyGgjPV1NalTR47+TlSZV6lklXLENbepszHsJUkx6FWO9UVGgAY8fE
	pc9iLtHogLlsck=
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:mime-version:from:date:message-id:subject:to
	:content-type; s=default; bh=1vNeCym/JZMXRjhoAZqvp8AjqTo=; b=eSS
	UsVvdN8xJvKW2A38Yswz/0jrvKWMAKhNSrEpI0/nZChuQUggvO/eqdN0k8k1VHLF
	mWVuWxR+0cPmTZPKvZ8RJ7vO8qwjrSRBitSDaYdi+l+VdMNcZjQ+3on0q2keKlHG
	3INGv3/HvaVhWrafTPOy/c5kUJE1ZOQ1bFxVWIY0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=medical, Medical, Electronic, en.wikipedia.org
X-HELO: mail-wr1-f54.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:from:date:message-id:subject:to;        bh=FJa932yqPqEHCOmLCgl5fyxJspt4/kgYE94RQ/w7l+8=;        b=XXVf9dC8j/GafpQNg9mMXl5NZ5kG63/vqXLtN1ZwZytmbV0lvqLL8at5Wiosx0tsY4         XYdOXZ1jL4hYNJdWe+8JKzDZhG0ClyYrwR6bZJ1FFrX0TtTG+Kp4uC95iykFxPxN9nNF         ruX8jnQvpXpL1WRhq6yYh9/oTKxLxsUjbM+7RiBbIPVkz9i8u1f3f5d76K719CGQWbtj         lDE+hoOgJOV9N31kLyp/dqtdbwK2+IBf02qtlYkD7CpaTx5eQboTyr/Z0Ize4ezP06kj         sWVB583jMyWGuwBTKDLM6QmntMb4N+zTtCFlYl33WvkkJsKOAlxv3OwsSGptrTl5CD5+         Yrng==
MIME-Version: 1.0
From: Sam Habiel <sam.habiel@gmail.com>
Date: Mon, 26 Nov 2018 14:07:46 -0500
Message-ID: <CABHT96207sag6z7LMMDiBQciu-B3o7zFoOkYLw3OOSi_S=Kckg@mail.gmail.com>
Subject: 32 bit vs 64 bit Cygwin, followup
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

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.

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.

--Sam

--
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

