public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: disable gdb.cp/call-method-register.exp when not using gcc
Date: Fri, 11 Nov 2022 09:17:48 +0000 (GMT)	[thread overview]
Message-ID: <20221111091748.1A6A5383469A@sourceware.org> (raw)

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

commit db2e277d1a840091f56185d94f9d39c6736d2556
Author: Bruno Larsen <blarsen@redhat.com>
Date:   Tue Oct 4 19:02:31 2022 +0200

    gdb/testsuite: disable gdb.cp/call-method-register.exp when not using gcc
    
    The test gdb.cp/call-method-register.exp assumes that the class will be
    placed on a register. However, this keyword has been deprecated since
    C++11, and Clang, for instance, does not feel the need to follow it.
    Since this test is not usable without this working, this commit marks
    this test as untested.
    
    Approved-by: Tom Tromey <tom@tromey.com>

Diff:
---
 gdb/testsuite/gdb.cp/call-method-register.exp | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gdb/testsuite/gdb.cp/call-method-register.exp b/gdb/testsuite/gdb.cp/call-method-register.exp
index a1e6498d66c..a98b11e4c11 100644
--- a/gdb/testsuite/gdb.cp/call-method-register.exp
+++ b/gdb/testsuite/gdb.cp/call-method-register.exp
@@ -26,6 +26,11 @@ if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} {
     return -1
 }
 
+if {![test_compiler_info gcc-*-* c++]} {
+    untested "test relies on a gcc extension"
+    return
+}
+
 proc test_call_register_class {} {
     global gdb_prompt

                 reply	other threads:[~2022-11-11  9:17 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=20221111091748.1A6A5383469A@sourceware.org \
    --to=blarsen@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).