public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marcelo at brs dot ind.br" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/63433] New: init_priority not working on ARM target Date: Wed, 01 Oct 2014 16:43:00 -0000 [thread overview] Message-ID: <bug-63433-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63433 Bug ID: 63433 Summary: init_priority not working on ARM target Product: gcc Version: 4.8.4 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: marcelo at brs dot ind.br Target: ARM I think this was started on bug #46770 (already closed). In 4.8.4 ARM target, init_priority is not working across TUs. I have a class declared on a static library with "__attribute__ ((init_priority (101)))". On main project i have another class declared with no attributes. The main project's class constructor is called before the static library class. In bug #46770 there's a comment that say that library's constructors will always be called after main project. But this is wrong by description of init_priority attribute. Both files (main e library) are compiled with 4.8.4 gcc version. Both creates init_array structs. Is there a way to change constructor order?
next reply other threads:[~2014-10-01 16:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-01 16:43 marcelo at brs dot ind.br [this message] 2015-01-15 10:45 ` [Bug c++/63433] " ramana 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-63433-4@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).