public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-8092] libstdc++: Fix incorrect branch prediction hint in std::stacktrace Date: Mon, 11 Apr 2022 21:11:48 +0000 (GMT) [thread overview] Message-ID: <20220411211148.98C0B3858C27@sourceware.org> (raw) https://gcc.gnu.org/g:b1124648ff8f655307f264d7b353fd68e3b03e9c commit r12-8092-gb1124648ff8f655307f264d7b353fd68e3b03e9c Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Apr 11 20:13:44 2022 +0100 libstdc++: Fix incorrect branch prediction hint in std::stacktrace libstdc++-v3/ChangeLog: * include/std/stacktrace (basic_stacktrace::_Impl::_M_allocate): Change [[unlikely]] attribute to [[likely]]. Diff: --- libstdc++-v3/include/std/stacktrace | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libstdc++-v3/include/std/stacktrace b/libstdc++-v3/include/std/stacktrace index dd78c71c5dc..79038e803f2 100644 --- a/libstdc++-v3/include/std/stacktrace +++ b/libstdc++-v3/include/std/stacktrace @@ -579,7 +579,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION { __try { - if (0 < __n && __n <= _S_max_size(__alloc)) [[unlikely]] + if (0 < __n && __n <= _S_max_size(__alloc)) [[likely]] { _M_frames = __alloc.allocate(__n); _M_capacity = __n;
reply other threads:[~2022-04-11 21:11 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220411211148.98C0B3858C27@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).