http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770
--- Comment #26 from H.J. Lu <hjl.tools at gmail dot com> 2010-12-11 20:16:56 UTC --- (In reply to comment #24) > Well, it sounds to me, then, that we would be introducing a binary > compatibility problem to make this change. If we're going to do it, I > think that means adding linker smarts that detect that there are both > .ctor.* and .init_array.* sections and issuing an error -- not a warning > -- together with a hint as to how to recompile so as to get either the > new or old behavior. (Some people will have binary libraries they can't > recompile, so we need to explain how to compile new code so that it > still uses .ctor.*.) Another thing, you have a binary archive with constructor priorities and you want to "interleave" your constructor priority with it: 1. It may not be possible due to priority integer. 2. You have to look at section name. 3. If a library uses .init_array, the priority digit in section name is different from the source. I don't think GCC really supports interleaving constructor priority at binary level. Unless GCC can guarantees one can interleave constructor priority in object files, I don't think we should worry about it with .init_array.
