public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Date: Fri, 04 Apr 2014 08:40:00 -0000	[thread overview]
Message-ID: <533E7010.2010202@users.sourceforge.net> (raw)
In-Reply-To: <loom.20140403T003453-906@post.gmane.org>

On 2014-04-02 18:03, Colin wrote:
> The problem I have can be reduced to this: I compile a simple "Hello
> World" console mode c program. I copy the .exe file and cygwin1.dll onto
> an embedded PC, open a console window, and run the program. The program
> runs, and returns immediately to the command prompt, with no output. No
> error messages, no nothing...
>
> The embedded PC is currently running a full installation of Windows XP
> Professional, SP3. It does so quite happily. It's CPU is DM&P Vortex86MX+
> 933MHz. I am able to run a "Hello World" program compiled with a native
> Windows compiler on it successfully.
>
> In discussing this with the embedded PC supplier, he suggests that the
> cygwin1.dll is exiting because it doesn't recognise the CPU.

Actually, if Wikipedia[1] is correct (yes, yes, I know), the problem is 
that the CPU doesn't recognize the code.  Apparently, these CPUs are 
missing the CMOV instruction used when compiling with gcc -march=i686, 
which has been the default setting for the Cygwin x86 compilers for 
several years now.

Therefore, in order to even attempt to make this work, you would have to 
recompile gcc for -march=i586 default, then rebuild *everything* with 
that gcc; but I can't guarantee that there won't be other issues as well.


Yaakov

[1] https://en.wikipedia.org/wiki/Vortex86#CPU


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

  parent reply	other threads:[~2014-04-04  8:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 19:20 Colin
2014-04-03 21:22 ` René Berber
2014-04-04  8:07   ` Colin
2014-04-04  8:34 ` Corinna Vinschen
2014-04-04  9:44   ` Colin
2014-04-04 11:37     ` Corinna Vinschen
2014-04-07 11:08       ` Colin
2014-04-07 11:23         ` Corinna Vinschen
2014-04-07 16:30           ` Larry Hall (Cygwin)
2014-04-07 21:10             ` Colin
2014-04-07 22:12               ` Larry Hall (Cygwin)
2014-04-07 22:49                 ` Peter A. Castro
2014-04-08  1:28                   ` Larry Hall (Cygwin)
2014-04-08  1:50                     ` Christopher Faylor
2014-04-08  1:59                       ` Larry Hall (Cygwin)
2014-04-15 21:52                         ` Peter A. Castro
2014-04-16 13:21                           ` Achim Gratz
2014-04-16 16:02                             ` Peter A. Castro
2014-04-16 16:20                               ` Achim Gratz
2014-04-08  2:14                       ` Peter A. Castro
2014-04-07 23:26                 ` Duncan Roe
2014-04-14  8:37                 ` Colin
2014-04-04  8:40 ` Yaakov (Cygwin/X) [this message]
2014-04-04  9:57   ` Colin

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=533E7010.2010202@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --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).