public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Felix Willgerodt <fwillger@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb, btrace: Fix rn-dl-bind.exp for new icx remark.
Date: Fri, 11 Nov 2022 12:33:12 +0000 (GMT)	[thread overview]
Message-ID: <20221111123313.9465B3858D20@sourceware.org> (raw)

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

commit 70b9d05b26e861524d70ee90dcd28cfd77032ddd
Author: Felix Willgerodt <felix.willgerodt@intel.com>
Date:   Thu Nov 10 16:22:46 2022 +0100

    gdb, btrace: Fix rn-dl-bind.exp for new icx remark.
    
    When running the test with the latest Intel compiler:
    
    Running gdb/gdb/testsuite/gdb.btrace/rn-dl-bind.exp ...
    gdb compile failed, icpx: warning: treating 'c' input as 'c++' when
    in C++ mode, this behavior is deprecated [-Wdeprecated]
    
    The test doesn't seem to test something specifically for C++,
    so I removed the C++ compilation option. Alternatively we could rename
    rn-dl-bind.exp.c to rn-dl-bind.exp.cc.
    
    Signed-off-by: Felix Willgerodt <felix.willgerodt@intel.com>

Diff:
---
 gdb/testsuite/gdb.btrace/rn-dl-bind.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.btrace/rn-dl-bind.exp b/gdb/testsuite/gdb.btrace/rn-dl-bind.exp
index d78f5654131..eb486b33124 100644
--- a/gdb/testsuite/gdb.btrace/rn-dl-bind.exp
+++ b/gdb/testsuite/gdb.btrace/rn-dl-bind.exp
@@ -28,7 +28,7 @@ if { [skip_btrace_tests] } {
 
 standard_testfile
 if [prepare_for_testing "failed to prepare" $testfile $srcfile \
-	{c++ debug ldflags=-Wl,-z,lazy}] {
+	{debug ldflags=-Wl,-z,lazy}] {
     return -1
 }

                 reply	other threads:[~2022-11-11 12:33 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=20221111123313.9465B3858D20@sourceware.org \
    --to=fwillger@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).