[Bug c++/63433] New: init_priority not working on ARM target

[Bug c++/63433] New: init_priority not working on ARM target

[marcelo at brs dot ind.br]

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?

[Bug c++/63433] init_priority not working on ARM target

[ramana at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63433

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-01-15
                 CC|                            |ramana at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
Please follow instructions on reporting bugs on the gcc website and provide a
self contained testcase that shows your problem.