public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adivilceanu at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54791] AIX-only: Constructors are not called in main program. Date: Mon, 05 Nov 2012 14:34:00 -0000 [thread overview] Message-ID: <bug-54791-4-wdSquMk33u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54791-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54791 --- Comment #10 from Adi <adivilceanu at yahoo dot com> 2012-11-05 14:34:25 UTC --- I found the real problem ! Now it can be reproducible even with a small test case. I can summarize it like this: If you have a global object/function defined in "n" different object files, then the constructors in the "n-1" object files might not be invoked at all. This will happen always for sure if the object/function is the first thing defined in those object files. Explination: Each object file when complied with g++ for AIX, will get a _GLOBAL__I_65535_0__***name_of_first_object_defined_in_this_compilation unit***. Now if there are 2 object file that have defined in them an object/function with the same name/signature then these 2 object files will get the same _GLOBAL__* symbol. Now later when the collect2 is involved it will take just one _GLOBAL__* into account. It will ignore the other n-1 symbols and so n-1 object remain with all their object's constructors not called. Given the above I have fixed my project not to have this situation(object with same name in multiple compilation units) and every constructor in my project is called now ! So it has nothing to do with inline as I first suspected. My inline sub-problem just was a side-effect of the real problem. Do you consider this being a bug? I think it is. Even if no fix is provided at least for me now something that would have been very usefull is if collect2 would have issued a more explicit message like "Multiple definitions of global objects with the same name; Some global objects will not be initialied !". I mean in the collect2 it is known that if it encounters this situation that there will be objects that will remain not-initialized. Right? Now that I solve this problem I have one new problem: It is related to the order of initialization of global objects across multiple compilation units. Shout I continue on this thread or open a new one? I am not sure its a bug.. I first have some questions on it.
next prev parent reply other threads:[~2012-11-05 14:34 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-03 9:20 [Bug c++/54791] New: " adivilceanu at yahoo dot com 2012-10-03 9:40 ` [Bug target/54791] " paolo.carlini at oracle dot com 2012-10-03 13:47 ` dje at gcc dot gnu.org 2012-11-02 14:49 ` adivilceanu at yahoo dot com 2012-11-02 14:52 ` adivilceanu at yahoo dot com 2012-11-03 6:21 ` adivilceanu at yahoo dot com 2012-11-03 6:24 ` adivilceanu at yahoo dot com 2012-11-03 13:49 ` dje at gcc dot gnu.org 2012-11-03 19:15 ` adivilceanu at yahoo dot com 2012-11-03 22:48 ` dje at gcc dot gnu.org 2012-11-05 14:34 ` adivilceanu at yahoo dot com [this message] 2012-11-05 18:55 ` dje at gcc dot gnu.org 2012-11-05 21:14 ` adivilceanu at yahoo dot com 2012-11-06 14:46 ` dje at gcc dot gnu.org 2012-11-06 16:23 ` adivilceanu at yahoo dot com 2012-11-06 21:50 ` adivilceanu at yahoo dot com 2012-11-07 1:27 ` dje at gcc dot gnu.org 2012-11-07 14:46 ` adivilceanu at yahoo dot com 2012-11-07 15:25 ` adivilceanu at yahoo dot com 2012-11-07 22:15 ` dje at gcc dot gnu.org 2012-11-13 8:21 ` adivilceanu at yahoo dot com 2012-11-13 8:30 ` adivilceanu at yahoo dot com 2012-11-13 14:03 ` dje at gcc dot gnu.org 2012-11-13 14:09 ` adivilceanu at yahoo dot com 2012-11-14 14:20 ` dje at gcc dot gnu.org 2012-11-27 15:54 ` adivilceanu at yahoo dot com 2012-11-27 18:55 ` adivilceanu at yahoo dot com 2012-11-27 19:01 ` adivilceanu at yahoo dot com 2012-11-27 20:42 ` dje at gcc dot gnu.org 2012-11-28 14:01 ` adivilceanu at yahoo dot com 2012-11-28 19:35 ` dje at gcc dot gnu.org 2012-11-29 9:35 ` adivilceanu at yahoo dot com 2012-11-29 9:44 ` adivilceanu at yahoo dot com 2012-12-01 21:42 ` dje at gcc dot gnu.org 2015-03-18 12:42 ` dje at gcc dot gnu.org 2015-03-18 12:49 ` dje at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-54791-4-wdSquMk33u@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).