From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com, Andrey Repin <anrdaemon@yandex.ru>,
Kaz Kylheku <920-082-4242@kylheku.com>
Subject: Re: Using ARM GNU GCC with Cygwin
Date: Sat, 4 Apr 2020 17:56:37 -0400 [thread overview]
Message-ID: <6daa2aa8-b2b6-1f71-c787-06340d05644e@cs.umass.edu> (raw)
In-Reply-To: <1239492934.20200405004017@yandex.ru>
On 4/4/2020 5:40 PM, Andrey Repin wrote:
> Greetings, Kaz Kylheku!
>
>> On 2020-04-04 02:00, Ben wrote:
>>> Is there something else I'm missing?
>
>> That by cross-compiling for your targets on Cygwin instead of a real
>> POSIX OS, you will something like double your compile times, if not
>> more.
>
> Proof, please.
I would agree with the statement, at least subjectively. There are various
things that I build on Linux, even in Linux virtual machines running on the
same Windows laptop, and Cygwin builds take perceptibly longer. Some of
this is down to the cost of fork() no doubt -- configure, and perhaps gcc
itself, tend to spin off lots of short jobs, which tends to expose the
fork overhead. Not sure if anything else is slower. Obviously the main
part of the computation in the compiler is the same.
Regards - Eliot Moss
next prev parent reply other threads:[~2020-04-04 21:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 9:00 Ben
2020-04-04 10:23 ` Eliot Moss
2020-04-04 18:15 ` Ben
2020-04-04 14:32 ` Kaz Kylheku
2020-04-04 18:18 ` Ben
2020-04-04 18:58 ` Åke Rehnman
2020-04-04 19:10 ` Ben
2020-04-04 20:39 ` Marco Atzeri
2020-04-08 20:50 ` Kaz Kylheku
2020-04-08 20:58 ` David Rothenberger
2020-04-08 21:13 ` Ben Kamen
2020-04-09 0:33 ` Kaz Kylheku
2020-04-09 0:17 ` Kaz Kylheku
2020-04-04 21:40 ` Andrey Repin
2020-04-04 21:56 ` Eliot Moss [this message]
2020-04-05 8:49 ` Csaba Raduly
2020-04-07 17:36 ` Ben
2020-04-04 19:11 ` Åke Rehnman
2020-04-04 19:31 ` Åke Rehnman
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=6daa2aa8-b2b6-1f71-c787-06340d05644e@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=920-082-4242@kylheku.com \
--cc=anrdaemon@yandex.ru \
--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).