PR c++/52477 - Wrong initialization order __attribute__((constructor)) vs static...

* doc/extend.texi (attribute constructor): Document present limitation.

From-SVN: r246288

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 77952ffea1c51b524d7eef1237688292453fc5ad..188a561963b5aa7a5febd98deef4ceac37fd780c 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2017-03-20  Martin Sebor  <msebor@redhat.com>
+
+       PR c++/52477
+       * doc/extend.texi (attribute constructor): Document present limitation.
+
 2017-03-20  Kelvin Nilsen  <kelvin@gcc.gnu.org>
 
        PR target/79963

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 143a7b7eb617ebdb86399ab4a1d8b8f5512fbe10..dbeec60bd5480e133f2de509bf2f7a2916c68f72 100644 (file)
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -2510,7 +2510,11 @@ if you have a constructor that allocates a resource and a destructor
 that deallocates the same resource, both functions typically have the
 same priority.  The priorities for constructor and destructor
 functions are the same as those specified for namespace-scope C++
-objects (@pxref{C++ Attributes}).
+objects (@pxref{C++ Attributes}).  However, at present, the order in which
+constructors for C++ objects with static storage duration and functions
+decorated with attribute @code{constructor} are invoked is unspecified.
+In mixed declarations, attribute @code{init_priority} can be used to
+impose a specific ordering.
 
 @item deprecated
 @itemx deprecated (@var{msg})