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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 20 Mar 2022 18:32:03 +0100 From: Andreas Schwab <schwab@...ux-m68k.org> To: John Crispin <john@...ozen.org> Cc: trix@...hat.com, toke@...e.dk, kvalo@...nel.org, davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ath9k: initialize arrays at compile time On Mär 20 2022, John Crispin wrote: > If I recall correctly { 0 } will only set the first element of the > struct/array to 0 and leave random data in all others elements An initializer always initializes the _whole_ object. The subject is also wrong, all initializers are executed at run time (automatic variables cannot be initialized at compile time). -- Andreas Schwab, schwab@...ux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Powered by blists - more mailing lists