summaryrefslogtreecommitdiffstats
path: root/linker/README.TXT
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Fix the C library initialization to avoid calling static C++ ↵David 'Digit' Turner2009-06-031-43/+0
| | | | | | constructors twice." This reverts commit 03eabfe65e1e2c36f4d26c78a730fa19a3bdada3.
* Fix the C library initialization to avoid calling static C++ constructors twice.David 'Digit' Turner2009-06-021-0/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | The problem was due to the fact that, in the case of dynamic executables, the dynamic linker calls the DT_PREINIT_ARRAY, DT_INIT and DT_INIT_ARRAY constructors when loading shared libraries and dynamic executables, *before* calling the executable's entry point (i.e. arch-$ARCH/bionic/crtbegin_dynamic.c) which in turns call __libc_init() in libc.so, as defined by bionic/libc_init_dynamic.c The latter did call these constructors array again, mistakenly. The patch also updates the documentation of many related functions. Also adds a new section to linker/README.TXT explaining restrictions on C library usage. The patch has been tested on a Dream for stability issues with proprietary blobs: - H264 decoding works - Camera + Video recording works - GPS works - Sensors work The tests in system/extra/tests/bionic/libc/common/test_static_cpp_mutex.cpp has been run and shows the static C++ constructor being called only once.
* Fix the parsing of the .fini_array in the dynamic linker (it should happen ↵David 'Digit' Turner2009-05-261-0/+114
in reverse order). Also add a small design overview document for the linker. The latter contains details on how the initialization/finalization is supposed to work.