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++/99077] New: [9/10/11 Regression] Cannot build libstdc++ with -fno-rtti Date: Thu, 11 Feb 2021 23:39:17 +0000 [thread overview] Message-ID: <bug-99077-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99077 Bug ID: 99077 Summary: [9/10/11 Regression] Cannot build libstdc++ with -fno-rtti Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- In file included from /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/iosfwd:38, from /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/ios:38, from /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:30: /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc: In function ‘void std::__throw_ios_failure(const char*, int)’: /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:174:54: error: no matching function for call to ‘std::ios_base::failure::failure(char*, int&)’ 174 | { _GLIBCXX_THROW_OR_ABORT(__ios_failure(_(str), err)); } | ^ /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:93:3: note: candidate: ‘std::ios_base::failure::failure(const char*, const std::error_code&)’ 93 | ios_base::failure::failure(const char* __str, const error_code& __ec) | ^~~~~~~~ /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:93:67: note: no known conversion for argument 2 from ‘int’ to ‘const std::error_code&’ 93 | ios_base::failure::failure(const char* __str, const error_code& __ec) | ~~~~~~~~~~~~~~~~~~^~~~ /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:90:3: note: candidate: ‘std::ios_base::failure::failure(const string&, const std::error_code&)’ 90 | ios_base::failure::failure(const string& __str, const error_code& __ec) | ^~~~~~~~ /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:90:69: note: no known conversion for argument 2 from ‘int’ to ‘const std::error_code&’ 90 | ios_base::failure::failure(const string& __str, const error_code& __ec) | ~~~~~~~~~~~~~~~~~~^~~~ /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:87:3: note: candidate: ‘std::ios_base::failure::failure(const string&)’ 87 | ios_base::failure::failure(const string& __str) | ^~~~~~~~ /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:87:3: note: candidate expects 1 argument, 2 provided In file included from /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/ios:42, from /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:30: /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/ios_base.h:255:34: note: candidate: ‘std::ios_base::failure::failure(const std::ios_base::failure&)’ 255 | class _GLIBCXX_ABI_TAG_CXX11 failure : public system_error | ^~~~~~~ /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/ios_base.h:255:34: note: candidate expects 1 argument, 2 provided /home/jwakely/src/gcc/gcc/libstdc++-v3/src/c++11/cxx11-ios_failure.cc:174:58: warning: ‘noreturn’ function does return 174 | { _GLIBCXX_THROW_OR_ABORT(__ios_failure(_(str), err)); } | ^ make[3]: *** [Makefile:855: cxx11-ios_failure-lt.s] Error 1
next reply other threads:[~2021-02-11 23:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-11 23:39 redi at gcc dot gnu.org [this message] 2021-02-11 23:39 ` [Bug libstdc++/99077] " redi at gcc dot gnu.org 2021-02-11 23:42 ` redi at gcc dot gnu.org 2021-02-12 14:43 ` cvs-commit at gcc dot gnu.org 2021-02-12 14:50 ` [Bug libstdc++/99077] [9/10 " redi at gcc dot gnu.org 2021-03-29 20:02 ` cvs-commit at gcc dot gnu.org 2021-03-29 20:06 ` [Bug libstdc++/99077] [9 " redi at gcc dot gnu.org 2021-04-19 9:31 ` cvs-commit at gcc dot gnu.org 2021-04-19 9:39 ` 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-99077-4@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).