在 2020/11/26 下午11:23, Vlastimil Babka 写道:
>>>
>>> I tried that, and .text became significantly larger, for reasons which
>>> I didn't investigate ;)
>
> I found out that comparing whole .text doesn't often work as changes might be
> lost in alignment, or
> once in a while cross the alignment boundary and become exagerated.
> bloat-o-meter works nice though.
>
>> Uh, BTW, with the gcc 8.3.1 and centos 7, goto or continue version has same
>> size
>> on my side with or w/o DEBUG_LIST. But actually, this clean up patch could
>> add 10 bytes also with or w/o DEDBUG_LIST.
>>
>> Maybe related with different compiler?
>
> gcc (SUSE Linux) 10.2.1 20201117 [revision
> 98ba03ffe0b9f37b4916ce6238fad754e00d720b]
>
> ./scripts/bloat-o-meter vmscan.o.before mm/vmscan.o
> add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-1 (-1)
> Function old new delta
> isolate_lru_pages 1125 1124 -1
> Total: Before=57283, After=57282, chg -0.00%
>
> Not surprising, as I'd expect the compiler to figure out by itself that
> list_move + continue
> repeats and can be unified. The reason for goto to stay would be rather
> readability (subjective).
Hi Vlastimil,
Thanks for tool sharing! The gcc do give different.
My data is read from 'size' tool and isolate_lru_pages text size from 'objdump
-d'. Maybe a
same way like bloat-o-meter. :)
Thanks
Alex
