[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mingw-cross-env-list] New features: automatic "du", automatic log c
From: |
Tony Theodore |
Subject: |
Re: [Mingw-cross-env-list] New features: automatic "du", automatic log compression |
Date: |
Mon, 12 Sep 2011 20:06:39 +1000 |
On 4 September 2011 21:39, Volker Grabsch <address@hidden> wrote:
> Tony Theodore schrieb:
>> On 4 September 2011 08:04, Volker Grabsch <address@hidden> wrote:
>> > On my system (Debian/Testing on amd64), this produces:
>> >
>> > log/wxwidgets:du: 1737716 KiB
>> > log/gcc:du: 1551720 KiB
>>
>> Curiously, the size varies significantly:
>>
>> DFly- log/gcc:du: 1288086 KiB
>> FBSD- log/gcc:du: 1354568 KiB
>> OS X- log/gcc:du: 1001064 KiB
>
> Note that gcc is compiled natively, so differences are to be
> expected.
>
> Maybe the sizes of *.o files vary a lot, probably due to
> differences in the generated assembly code, or different
> names (and thus name lengths) of the debug symbols.
>
> It would be more interesting to check for differences in
> the cross-compiled packages, because those are compiled
> by the same compiler on all systems.
>
>> I wonder if this it caused by the difference in block size between
>> filesystems?
>
> That is also possible, but would be more visible on purely
> cross-compiled packages rather than natively compiled packages.
Good point, I'll report back if I get a chance to investigate further.
I've given up on the idea of generated binaries being identical, but
this should satisfy my curiosity for for a while.
Cheers,
Tony