From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Use init_priority attribute for Init object [PR 98108]
Date: Tue, 15 Dec 2020 18:44:08 +0000 [thread overview]
Message-ID: <20201215184408.GO2309743@redhat.com> (raw)
In-Reply-To: <20201215114715.GA865968@redhat.com>
On 15/12/20 11:47 +0000, Jonathan Wakely wrote:
>This causes the global objects that run the <iostream> initialization
>code to be constructed earlier, which avoids some bugs in user code due
>to incorrectly relying on static initialization order.
>
>libstdc++-v3/ChangeLog:
>
> PR libstdc++/98108
> * include/std/iostream (__ioinit): Add init_priority attribute.
>
I've reverted this because it doesn't work on darwin, and isn't
required for correctness anyway.
Tested powerpc64le-linux. Committed to trunk.
>commit cf4ed3b41594b6935a337fe0aaf8149eadf88751
>Author: Jonathan Wakely <jwakely@redhat.com>
>Date: Tue Dec 15 11:40:06 2020
>
> libstdc++: Use init_priority attribute for Init object [PR 98108]
>
> This causes the global objects that run the <iostream> initialization
> code to be constructed earlier, which avoids some bugs in user code due
> to incorrectly relying on static initialization order.
>
> libstdc++-v3/ChangeLog:
>
> PR libstdc++/98108
> * include/std/iostream (__ioinit): Add init_priority attribute.
>
>diff --git a/libstdc++-v3/include/std/iostream b/libstdc++-v3/include/std/iostream
>index f988342b90a..6b2f964f688 100644
>--- a/libstdc++-v3/include/std/iostream
>+++ b/libstdc++-v3/include/std/iostream
>@@ -70,8 +70,16 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> #endif
> //@}
>
>+#if __has_attribute(__init_priority__)
>+# define _GLIBCXX_INIT_PRIO(N) __attribute__((__init_priority__(N)))
>+#else
>+# define _GLIBCXX_INIT_PRIO(N)
>+#endif
>+
> // For construction of filebuffers for cout, cin, cerr, clog et. al.
>- static ios_base::Init __ioinit;
>+ static ios_base::Init __ioinit _GLIBCXX_INIT_PRIO(90);
>+
>+#undef _GLIBCXX_INIT_PRIO
>
> _GLIBCXX_END_NAMESPACE_VERSION
> } // namespace
prev parent reply other threads:[~2020-12-15 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 11:47 Jonathan Wakely
2020-12-15 18:44 ` Jonathan Wakely [this message]
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=20201215184408.GO2309743@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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: link
Be 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).