[Bug c/70060] array initialization adds to executable size

2016-03-03 Thread stsp at users dot sourceforge.net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70060 --- Comment #4 from Stas Sergeev --- (In reply to Jakub Jelinek from comment #3) > If you want it to be initialized at runtime, do that yourself. > The compiler can't do that, you could e.g. access bigarr from another > compilation unit before th

[Bug c/70060] array initialization adds to executable size

2016-03-03 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70060 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #3

[Bug c/70060] array initialization adds to executable size

2016-03-03 Thread stsp at users dot sourceforge.net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70060 --- Comment #2 from Stas Sergeev --- The question is not what happens now, but rather can't it be done differently? Is there any reason why gcc can't but it into .bss anyway, and initialize from the startup code? I realize this is not a bug but a

[Bug c/70060] array initialization adds to executable size

2016-03-03 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70060 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---