public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gustavo at ugr dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/91488] [9/10/11/12 Regression] char_traits::length causes "inlining failed in call to always_inline" error with -fgnu-tm -O2 -std=c++17 Date: Mon, 07 Jun 2021 08:14:45 +0000 [thread overview] Message-ID: <bug-91488-4-HOv4uJa81E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91488-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91488 --- Comment #6 from gustavo <gustavo at ugr dot es> --- the bug is still here in gcc versión 11.1.1 20210531 (Red Hat 11.1.1-3) (GCC) g++ -fgnu-tm -O1 -Wall bug.cc -o bug In file included from /usr/include/c++/11/ios:40, from /usr/include/c++/11/ostream:38, from /usr/include/c++/11/iostream:39, from bug.cc:2: /usr/include/c++/11/bits/char_traits.h: In static member function 'static constexpr std::size_t std::char_traits<char>::length(const char_type*)': /usr/include/c++/11/bits/char_traits.h:257:5: error: inlining failed in call to 'always_inline' 'constexpr bool std::__constant_string_p(const _CharT*) [with _CharT = char]': 257 | __constant_string_p(const _CharT* __s) | ^~~~~~~~~~~~~~~~~~~ /usr/include/c++/11/bits/char_traits.h:368:32: note: called from here 368 | if (__constant_string_p(__s)) | ~~~~~~~~~~~~~~~~~~~^~~~~ /usr/include/c++/11/bits/char_traits.h:257:5: error: inlining failed in call to 'always_inline' 'constexpr bool std::__constant_string_p(const _CharT*) [with _CharT = char]': 257 | __constant_string_p(const _CharT* __s) | ^~~~~~~~~~~~~~~~~~~ /usr/include/c++/11/bits/char_traits.h:368:32: note: called from here 368 | if (__constant_string_p(__s)) | ~~~~~~~~~~~~~~~~~~~^~~~~ make: *** [<builtin>: bug] Error 1
next prev parent reply other threads:[~2021-06-07 8:14 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91488-4@http.gcc.gnu.org/bugzilla/> 2020-11-16 22:03 ` [Bug libstdc++/91488] [9/10/11 " redi at gcc dot gnu.org 2021-01-14 8:19 ` rguenth at gcc dot gnu.org 2021-06-01 8:15 ` [Bug libstdc++/91488] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-06-07 8:11 ` gustavo at ugr dot es 2021-06-07 8:14 ` gustavo at ugr dot es [this message] 2021-06-07 8:16 ` gustavo at ugr dot es 2021-06-17 21:45 ` cvs-commit at gcc dot gnu.org 2021-06-18 10:20 ` [Bug libstdc++/91488] [9/10/11 " cvs-commit at gcc dot gnu.org 2021-06-18 11:50 ` [Bug libstdc++/91488] [9/10 " cvs-commit at gcc dot gnu.org 2021-06-18 14:43 ` cvs-commit at gcc dot gnu.org 2021-06-18 14:45 ` 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-91488-4-HOv4uJa81E@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: 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).