public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "David Allsopp" <David.Allsopp@cl.cam.ac.uk>
To: <cygwin@cygwin.com>
Subject: RE: Cygwin x86 on Windows 10 ARM64
Date: Tue, 10 Jul 2018 20:25:00 -0000	[thread overview]
Message-ID: <004401d4188c$17986b60$46c94220$@cl.cam.ac.uk> (raw)
In-Reply-To: <e4cb08a5-3db8-7a0b-edbd-de4fec1fc5fc@SystematicSw.ab.ca>

Brian Inglis wrote:
> On 2018-07-10 03:51, David Allsopp wrote:
> > I've been trying out the x86 emulation in Microsoft's ARM64 version of
> > Windows 10 1803.
> >
> > I had two issues with Cygwin x86. The first, which is simple, is that
> > Windows doesn't by default create C:\Windows\SysWOW64\drivers\etc
> > which causes /etc/postinstall/base-files-mketc.sh to exit with an
> > error all the time. I wonder if there's a possible workaround to make
> that less intrusive?
> > The error message implies that it may have computed the wrong
> > directory, which it hasn't - it's just that the directory doesn't exist.
> 
> Do C:\Windows\{System32,SysNative,Sys*}\drivers\etc exist under the
> emulator?
> What does "cygpath -SU" show?

cygpath -SU gives /proc/cygdrive/c/Windows/SysWOW64

Checking within C:\Windows\SysWOW64\cmd.exe (i.e. x86 cmd):

C:\Windows\System32\drivers\etc exists and contains expected files
C:\Windows\Sysnative\drivers\etc exists and contains expected files (looks identical to System32, as you'd hope)
C:\Windows\SysArm32\drivers does not contain an etc directory (but wasn't referenced)
C:\Windows\SysWOW64\drivers didn't contain an etc directory (I created one to silence the error)

So perhaps on WOW64 it would be worth falling back to Sysnative if etc isn't found? Or even just using Sysnative by default in WOW64?

> > The other is that all Cygwin binaries are emitting the "Could not
> > compute FAST_CWD pointer" warning.
> 
> It is just a warning and everything should run normally: what would
> normally be an ntdll entry point on x86 is probably a thunk or trampoline
> to
> arm64(ISA)/aarch64(mode)/armv8(design) code.

Does it potentially make anything slower? (being slightly lazy - I could look at the code and see precisely what it's for).


David


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

  reply	other threads:[~2018-07-10 20:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10  9:51 David Allsopp
2018-07-10 13:04 ` Corinna Vinschen
2018-07-11 16:13   ` Brian Inglis
2018-07-12 11:04   ` David Allsopp
2018-07-12 12:04     ` Corinna Vinschen
2018-07-12 13:34       ` David Allsopp
2018-07-12 16:35         ` David Allsopp
2018-07-12 18:24           ` Corinna Vinschen
2018-07-10 17:12 ` Brian Inglis
2018-07-10 20:25   ` David Allsopp [this message]
2018-07-10 21:50     ` Andrey Repin
2018-07-11  8:14       ` Corinna Vinschen
2018-07-11 12:34         ` David Allsopp

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='004401d4188c$17986b60$46c94220$@cl.cam.ac.uk' \
    --to=david.allsopp@cl.cam.ac.uk \
    --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).