From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)
Date: Fri, 20 Mar 2020 20:24:37 +0100 [thread overview]
Message-ID: <8a6c6dcd-c235-a2bd-1437-c7efa8ba529b@t-online.de> (raw)
In-Reply-To: <f88b5a5d-279a-7765-574f-a9cbbef540c6@SystematicSw.ab.ca>
Am 20.03.2020 um 00:18 schrieb Brian Inglis:
> On 2020-03-18 23:25, Marco Atzeri via Cygwin wrote:
>> It seems something is adding 5M or more to the normal
>> size of the programs
>
> See attached for summary details by arch, but main points for both are, on x86_64:
[...]
Could this be due to the ginormous number of targets configured into the
build?
Asking the tools themselves about the list of targets they support,
compared to a run-off-the-mill default native build from current git
sources, yields:
> hbbro@NB5 ~/src/gnu/binutils/bld/gcc/binutils
> $ objdump -i | wc
> 8172 30919 441168
>
> hbbro@NB5 ~/src/gnu/binutils/bld/gcc/binutils
> $ ./objdump -i | wc
> 117 325 2831
That size difference evidently due to the 260+ supported output target
types in /usr/bin/objdump.exe, compared to 22 in my own build.
To put it another way the individual object files in libbfd.a are of
quite similar size; there just a whole lot more of them, and that
explains the difference.
next prev parent reply other threads:[~2020-03-20 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 0:25 Steven Penny
2020-03-19 5:25 ` Marco Atzeri
2020-03-19 23:18 ` Brian Inglis
2020-03-20 19:24 ` Hans-Bernhard Bröker [this message]
2020-03-21 4:55 ` Marco Atzeri
2020-03-21 6:40 ` Marco Atzeri
2020-03-22 20:19 ` Yaakov Selkowitz
2020-03-22 23:05 ` Marco Atzeri
2020-04-01 11:33 ` Jan Nijtmans
2020-04-06 10:07 ` Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)] Jan Nijtmans
2020-04-06 23:55 ` JonY
2020-04-07 0:57 ` Yaakov Selkowitz
2020-04-07 10:29 ` JonY
-- strict thread matches above, loose matches on Subject: below --
2020-03-15 10:33 [ANNOUNCEMENT] Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64) JonY via Cygwin-announce
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=8a6c6dcd-c235-a2bd-1437-c7efa8ba529b@t-online.de \
--to=hbbroeker@t-online.de \
--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).