full-disclosure - 1 advantage for implicit static storage init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20020915170546.C7787@hamsec.aurora.sfo.interquest.net>
From: silvio at big.net.au (silvio@....net.au)
Subject: 1 advantage for implicit static storage init

ok.. 1 advantage that is possible with implicit initialization..

if a c compiler does not realize it is a zero initialization, it may
put the data in initializated data segment.

if its not initialized, it will put it in the bss.

since the bss is rather implicit and doesnt carry weight in the binary,
the bss obviously allows for binary size to shrink.  (looking at unix).

i think this is shortcuting for no reason though :)

--
Silvio