32 bit vs 64 bit Cygwin, followup
Wed Nov 28 16:06:00 GMT 2018
Are you telling me that gcc has a flag to support AMD ABI on Cygwin
x64? The assembly code is not standalone; it gets called from C code
and calls C code.
On Wed, Nov 28, 2018 at 11:01 AM Yaakov Selkowitz <firstname.lastname@example.org> wrote:
> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin