From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Native ARM support for Cygwin
Date: Wed, 8 Dec 2021 12:12:12 +0100 [thread overview]
Message-ID: <YbCTDCoooa0XQnHj@calimero.vinschen.de> (raw)
In-Reply-To: <1918386184.561539.1638929253143@mail.yahoo.com>
On Dec 8 02:07, Aaron Franke via Cygwin wrote:
> Hello Cygwin,
> I am wondering what are the plans for adding support for native ARM64
> Windows to Cygwin.
> Currently there are only downloads for x86 (both 32-bit and 64-bit),
> but not for ARM.
> I do see in the FAQ that there is a mention of how ARM systems can run
> the x86 version of Cygwin, however I am interested in a native ARM64
> toolchain if possible. By the way, I'm only interested in 64-bit ARM.
No plans. To create an ARM64 version of Cygwin we need:
- Toolchains (binutils, gcc, gdb) targeting aarch64-pc-cygwin
and aarch64-w64-mingw32.
I don't know if the mingw toolchain already exists, but if so, the
Cygwin toolchain could be derived from there. The differences would
be basically the same as on x86_64 (sizeof(long), different default
link libs, etc)
- Make sure Mingw-w64 for ARM is working as desired, including the
special code for Cygwin in there. AFAIK, Mingw-w64 for ARM64 is still
in an experimental stage, but I could be wrong.
- Make sure to understand the differences between ARM64 ABI on Windows
vs. the default aarch64 ABI (if any).
- At least one person who's fluent in aarch64 assembler who will take a
stab at creating matching aarch64 assembler code snippets in places we
have x86 and x86_64 assembler today. We might get away with some
of the code being in newlib already (memset/memcpy).
- ARM64 Windows and hardware for testing.
I don't see anything of that happen any time soon ¯\_(ツ)_/¯
Corinna
next prev parent reply other threads:[~2021-12-08 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1918386184.561539.1638929253143.ref@mail.yahoo.com>
2021-12-08 2:07 ` Aaron Franke
2021-12-08 11:12 ` Corinna Vinschen [this message]
2021-12-10 14:18 ` Jon Turney
2021-12-10 14:58 ` Marco Atzeri
2021-12-10 15:34 ` Arthur Norman
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=YbCTDCoooa0XQnHj@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@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).