public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64}-gcc-7.3.0-1 (Test)
Date: Sat, 25 Aug 2018 04:55:00 -0000	[thread overview]
Message-ID: <5b809f2e.1c69fb81.9d88d.b1dd@mx.google.com> (raw)
In-Reply-To: <c80de729-677c-5125-e703-efb784e8febe@gmail.com>

On Fri, 24 Aug 2018 10:11:42, JonY wrote:
> Can you try breaking it down by phases?
> 1. Preprocessor phase with -E -o file.ii

    $ time x86_64-w64-mingw32-g++ -E -o file.ii stoi.cpp; wc -c file.ii
    real    0m0.172s
    719550 file.ii

> 2. Compile phase (compile output from phase 1) with -c

    $ time x86_64-w64-mingw32-g++ -c file.ii; wc -c file.o
    real    0m0.312s
    7368 file.o

> 3. Link phase, point gcc to the output from phase 2.

    $ time x86_64-w64-mingw32-g++ -static file.o; wc -c a.exe
    real    0m1.950s
    11906797 a.exe

Also it might be worth noting the starting point - for some reason Cygwin is 4
times larger than Msys2?

    $ wc -c /lib/gcc/x86_64-w64-mingw32/7.3.0/libstdc++.a
    22446354 /lib/gcc/x86_64-w64-mingw32/7.3.0/libstdc++.a

    $ wc -c mingw64/lib/gcc/x86_64-w64-mingw32/8.2.0/libstdc++.a
    5597192 mingw64/lib/gcc/x86_64-w64-mingw32/8.2.0/libstdc++.a


--
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-08-25  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 23:52 JonY
2018-08-21 15:16 ` Steven Penny
2018-08-24 19:06   ` JonY
2018-08-25  4:55     ` Steven Penny [this message]
2018-08-26 14:04       ` JonY
2018-08-27  3:32         ` Steven Penny
2018-08-26 15:17       ` Hans-Bernhard Bröker
2018-08-26 21:41         ` Steven Penny

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=5b809f2e.1c69fb81.9d88d.b1dd@mx.google.com \
    --to=svnpenn@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).