public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi 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, 11 Sep 2023 11:52:39 +0000	[thread overview]
Message-ID: <bug-111050-4-DRXslFbl1F@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 #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to François Dumont from comment #1)
> It seems to be a limited issue as you need a non-optimized build.

That's not a safe assumption. Inlining decisions can change across builds and
across architectures, and it's not safe to assume the affected functions will
always be inlined, e.g. in the presence of explicit instantiation definitions.

> The only
> impacted member is the _M_next() which is a simple static_cast, I'm very
> surprised that it's not always inlined even if non-optimized.

No functions are inlined for non-optimized builds, unless forced with
always_inline.

  parent reply	other threads:[~2023-09-11 11:52 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 [this message]
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
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-DRXslFbl1F@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).