public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111050] [11/12/13/14 Regression] ABI break in _Hash_node_value_base since GCC 11
Date: Mon, 02 Oct 2023 20:48:28 +0000 [thread overview]
Message-ID: <bug-111050-4-SJGQy6gUQN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111050-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111050
--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Francois Dumont
<fdumont@gcc.gnu.org>:
https://gcc.gnu.org/g:e6d26b141bf03a0348b51e4778c79d44dc760eed
commit r13-7931-ge6d26b141bf03a0348b51e4778c79d44dc760eed
Author: Tim Song <t.canens.cpp@gmail.com>
Date: Wed Sep 6 19:31:55 2023 +0200
libstdc++: Force _Hash_node_value_base methods inline to fix abi (PR111050)
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=1b6f0476837205932613ddb2b3429a55c26c409d
changed _Hash_node_value_base to no longer derive from _Hash_node_base,
which means
that its member functions expect _M_storage to be at a different offset. So
explosions
result if an out-of-line definition is emitted for any of the member
functions (say,
in a non-optimized build) and the resulting object file is then linked with
code built
using older version of GCC/libstdc++.
libstdc++-v3/ChangeLog:
PR libstdc++/111050
* include/bits/hashtable_policy.h
(_Hash_node_value_base<>::_M_valptr(),
_Hash_node_value_base<>::_M_v())
Add [[__gnu__::__always_inline__]].
(cherry picked from commit 2c1e3544a94c5d7354fad031e1f9731c3ce3af25)
next prev parent reply other threads:[~2023-10-02 20:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 14:40 [Bug libstdc++/111050] New: " rs2740 at gmail dot com
2023-08-17 15:03 ` [Bug libstdc++/111050] " redi at gcc dot gnu.org
2023-08-18 6:42 ` rguenth at gcc dot gnu.org
2023-09-01 20:33 ` fdumont at gcc dot gnu.org
2023-09-01 23:17 ` rs2740 at gmail dot com
2023-09-02 7:20 ` fdumont at gcc dot gnu.org
2023-09-06 17:17 ` fdumont at gcc dot gnu.org
2023-09-06 18:15 ` rs2740 at gmail dot com
2023-09-06 18:19 ` rs2740 at gmail dot com
2023-09-08 17:04 ` rs2740 at gmail dot com
2023-09-11 11:52 ` redi at gcc dot gnu.org
2023-09-11 16:59 ` frs.dumont at gmail dot com
2023-09-12 15:54 ` john at drouhard dot dev
2023-09-12 16:07 ` redi at gcc dot gnu.org
2023-09-28 17:24 ` cvs-commit at gcc dot gnu.org
2023-10-02 20:44 ` cvs-commit at gcc dot gnu.org
2023-10-02 20:47 ` cvs-commit at gcc dot gnu.org
2023-10-02 20:48 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-03 9:31 ` redi 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-111050-4-SJGQy6gUQN@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: 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).