public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: Using ARM GNU GCC with Cygwin
Date: Sun, 5 Apr 2020 10:49:49 +0200	[thread overview]
Message-ID: <CAEhDDbAXmMsJ=+8KstPVfftLyGhWnAYmtqyTQzyfwDgcPMDnUg@mail.gmail.com> (raw)
In-Reply-To: <1239492934.20200405004017@yandex.ru>

On Sat, Apr 4, 2020 at 11:50 PM Andrey Repin <anrdaemon@yandex.ru> 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.
>
>
This is not cross-compiling, but...

git clone https://github.com/eclipse/titan.core.git
cd titan.core
time make -j8

On Cygwin:

real    7m46.830s
user    22m3.272s
sys     3m33.598s

On WSL Ubuntu:

real    2m12.984s
user    5m11.656s
sys     2m16.875s

Csaba
-- 
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant
way
to get the wrong information: this is what you want. - Scott Meyers
(C++TDaWYK)

  parent reply	other threads:[~2020-04-05  8:50 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
2020-04-05  8:49     ` Csaba Raduly [this message]
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='CAEhDDbAXmMsJ=+8KstPVfftLyGhWnAYmtqyTQzyfwDgcPMDnUg@mail.gmail.com' \
    --to=rcsaba@gmail.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).