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: Sat, 03 Nov 2012 19:15:00 -0000 [thread overview] Message-ID: <bug-54791-4-woJ4SNVmXn@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 #8 from Adi <adivilceanu at yahoo dot com> 2012-11-03 19:14:41 UTC --- Thank you for your response. (Sorry for the repeated emails. I did it because I got delivery failures on the first 4 mails.) So just to be 100% sure on this: If I want to be sure all my constructors are called I should not have any of them inlined. Correct ? What about if I have a constructor body/implementation inside a class declaration ? Does the compiler inline that as well? I guess it might. So how do you see this case. Is it not a bug? I mean I am expecting my constructors to be called and they are not. Do you know a easy way to solve this without modifying all my constructors ? (any compiler options perhaps, ..using __attribute__((constructor)) ) ? PS: If I want to send you an attachment in a mail what format should it be ? txt, doc ? I got some delivery failures,... that's why I am asking. ________________________________ From: dje at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> To: adivilceanu@yahoo.com Sent: Saturday, November 3, 2012 3:48 PM Subject: [Bug target/54791] AIX-only: Constructors are not called in main program. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54791 --- Comment #7 from David Edelsohn <dje at gcc dot gnu.org> 2012-11-03 13:48:46 UTC --- The New York area has experienced a major natural disaster. I am located near NYC. GCC support is provided by volunteers. Repeatedly resending your message will not elicit a faster response. AIX uses the XCOFF file format, not ELF. The object files do not contain .ctor or .init sections to define constructors. The GCC collect2 wrapper scans object files for constructors and creates a function to call them. If the constructors are inlined, the symbols might not appear when the object files are scanned, preventing them from being included in the list of constructors to call.
next prev parent reply other threads:[~2012-11-03 19:15 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 [this message] 2012-11-03 22:48 ` dje at gcc dot gnu.org 2012-11-05 14:34 ` adivilceanu at yahoo dot com 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-woJ4SNVmXn@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).