public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/106659] [13 Regression] error: no member named 'fancy_abort' in namespace 'std'; did you mean simply 'fancy_abort' Date: Tue, 16 Aug 2022 22:25:09 +0000 [thread overview] Message-ID: <bug-106659-4-YHBqyVP6rV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106659-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106659 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|regression |gcov-profile CC| |marxin at gcc dot gnu.org Ever confirmed|0 |1 Summary|error: no member named |[13 Regression] error: no |'fancy_abort' in namespace |member named 'fancy_abort' |'std'; did you mean simply |in namespace 'std'; did you |'fancy_abort' |mean simply 'fancy_abort' Target Milestone|--- |13.0 Keywords| |build Last reconfirmed| |2022-08-16 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This should fix the issue: diff --git a/gcc/gcov-dump.cc b/gcc/gcov-dump.cc index 85b1be8859e..03023bfb226 100644 --- a/gcc/gcov-dump.cc +++ b/gcc/gcov-dump.cc @@ -17,6 +17,7 @@ along with Gcov; see the file COPYING3. If not see <http://www.gnu.org/licenses/>. */ #include "config.h" +#define INCLUDE_VECTOR #include "system.h" #include "coretypes.h" #include "tm.h" @@ -28,8 +29,6 @@ along with Gcov; see the file COPYING3. If not see #include "gcov-io.h" #include "gcov-io.cc" -#include <vector> - using namespace std; static void dump_gcov_file (const char *);
prev parent reply other threads:[~2022-08-16 22:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-16 22:00 [Bug regression/106659] New: " salvadore at FreeBSD dot org 2022-08-16 22:25 ` pinskia at gcc dot gnu.org [this message]
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-106659-4-YHBqyVP6rV@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).