[Bug ld/18914] Shared lib created using static libs and "-Wl,--exclude-libs,ALL" export uninitialized variables

2015-10-05 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=18914 H.J. Lu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug ld/18914] Shared lib created using static libs and "-Wl,--exclude-libs,ALL" export uninitialized variables

2015-10-05 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=18914 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a0d49154d4a471cd36954408b29a348a091efaa3 commit a0d49154d4a471cd36954408b29a348a

[Bug ld/18914] New: Shared lib created using static libs and "-Wl,--exclude-libs,ALL" export uninitialized variables

2015-09-03 Thread johan.bolmsjo at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=18914 Bug ID: 18914 Summary: Shared lib created using static libs and "-Wl,--exclude-libs,ALL" export uninitialized variables Product: binutils Ver

GNU ld: Uninitialized variables with "-Wl,--exclude-libs,ALL" global

2015-08-31 Thread Johan Bolmsjö
to be true for functions and initialized variables. Uninitialized variables however, e.g. a global variable "int foo;" are still global in the resulting shared library. The gold linker behaves according to the documentation and uninitialized variables are local in the resulting shared

uninitialized variables

2010-09-11 Thread Lucas Clemente Vella
These uninitialized variables in bfd/elf32-arm.c caused the compilation to fail with -Werror (the default) and -O3 (my choice) -- Lucas Clemente Vella lve...@gmail.com --- elf32-arm.c 2010-02-22 05:06:48.0 -0300 +++ ../../binutils-2.20.1-work/bfd/elf32-arm.c 2010-09-11 21:23