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.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
