public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Gary Benson <gary@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Fix compilation error with clang in gdb/testsuite/gdb.cp/exception.cc
Date: Mon, 20 Apr 2020 14:07:02 +0000 (GMT)	[thread overview]
Message-ID: <20200420140702.2EA33386F47D@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=25230285442ed10ec0f65d770d0a188ff8680b8f

commit 25230285442ed10ec0f65d770d0a188ff8680b8f
Author: Gary Benson <gbenson@redhat.com>
Date:   Mon Apr 20 15:05:01 2020 +0100

    Fix compilation error with clang in gdb/testsuite/gdb.cp/exception.cc
    
    Clang fails to compile the above file, with the following error:
      warning: using directive refers to implicitly-defined namespace 'std'
    
    This prevents the following testcase from executing:
      gdb.cp/exception.exp

Diff:
---
 gdb/testsuite/ChangeLog           | 4 ++++
 gdb/testsuite/gdb.cp/exception.cc | 2 --
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 8ee15208cea..a744a245be6 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2020-04-20  Gary Benson <gbenson@redhat.com>
+
+	* gdb.cp/exception.cc: Fix compilation error with clang.
+
 2020-04-20  Gary Benson <gbenson@redhat.com>
 
 	* gdb/testsuite/gdb.trace/tspeed.c: Fix compilation error with
diff --git a/gdb/testsuite/gdb.cp/exception.cc b/gdb/testsuite/gdb.cp/exception.cc
index 034c9dc8664..813c1605c06 100644
--- a/gdb/testsuite/gdb.cp/exception.cc
+++ b/gdb/testsuite/gdb.cp/exception.cc
@@ -17,8 +17,6 @@
 
 // Test file for exception handling support.
 
-using namespace std;
-
 int foo (int i)
 {
   if (i < 32)


                 reply	other threads:[~2020-04-20 14:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200420140702.2EA33386F47D@sourceware.org \
    --to=gary@sourceware.org \
    --cc=gdb-cvs@sourceware.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).