On Thu, Sep 18, 2014 at 8:32 PM, Jonathan Wakely <jwakely....@gmail.com> wrote:
>> ian3@jaguar:~/usr/libexec/gcc$ size i686-pc-linux-gnu/4.9.0/{cc1,f951}
>> text data bss dec hex filename
>> 14965183 23708 744944 15733835 f0144b
>> i686-pc-linux-gnu/4.9.0/cc1
>> 15882830 29264 750832 16662926 fe418e
>> i686-pc-linux-gnu/4.9.0/f951
>>
>> The phrase "dangerous GNU crap" comes to mind :-)
> If you say so. The size command is older than GNU, or BSD for that matter.
It's OK. A GNU can't be blamed for crapping, it's natural :-).
> Your OS probably has a man page for it.
It does. "Copyright (c) 1991-2013 Free Software Foundation, Inc."
But the man page doesn't tell me what the column headings actually
mean. And even if it did, why should I have to look up the manual to
find out what the headings mean? What's the point of headings? Since
they aren't even aligned, it might just as well leave the out
altogether: they're just a waste of screen space.
But I don't want to argue about GNU crap, it's a natural and
understandable phenomenon, and not particularly interesting. I want to
know what's in the GCC binaries. So let's focus on that.
What was the reason you suggested I look at the output of the size
command? What does that tell me about what is the cause of the holes
in the file, or the extra padding, or whatever it is you think is the
explanation for this phenomenon?
Ian
