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++/105671] [11/12/13 Regression] Unexplained "undefined reference" error
Date: Fri, 27 May 2022 14:23:26 +0000	[thread overview]
Message-ID: <bug-105671-4-8sT1VFoIle@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105671-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105671

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:de57440858591a88e8fd7ba2505ca54546c86021

commit r13-801-gde57440858591a88e8fd7ba2505ca54546c86021
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri May 27 12:43:18 2022 +0100

    libstdc++: Mark non-exported function always_inline [PR105671]

    This new function was added for gcc 11.1 but is not exported from the
    shared library. Depending on inlining decisions, its callers might get
    inlined but an external definition be needed for this function. That
    then fails to link.

    Since we can't add the export to the gcc-11 release branch now, mark it
    always_inline. We can consider exporting it for gcc-13 if/when we bump
    the shared library version (and maybe also for gcc-12 which is currently
    at the same version as trunk). For now, the attribute will solve the
    problem on all affected branches. The function is small enough that
    force-inlining it shouldn't cause problems.

    libstdc++-v3/ChangeLog:

            PR libstdc++/105671
            * include/std/sstream (basic_stringbuf::_M_high_mark): Add
            always_inline attribute.

  parent reply	other threads:[~2022-05-27 14:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 10:06 [Bug c++/105671] New: " christian.morales.vega at gmail dot com
2022-05-20 10:08 ` [Bug c++/105671] " christian.morales.vega at gmail dot com
2022-05-26 23:09 ` [Bug libstdc++/105671] [11/12/13 Regression] " jsm28 at gcc dot gnu.org
2022-05-27 10:19 ` redi at gcc dot gnu.org
2022-05-27 13:51 ` christian.morales.vega at gmail dot com
2022-05-27 14:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-27 14:25 ` [Bug libstdc++/105671] [11/12 " redi at gcc dot gnu.org
2022-06-08 15:53 ` cvs-commit at gcc dot gnu.org
2022-06-08 16:10 ` [Bug libstdc++/105671] [11 " redi at gcc dot gnu.org
2022-07-07 23:33 ` cvs-commit at gcc dot gnu.org
2022-07-07 23:34 ` 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-105671-4-8sT1VFoIle@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).