public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>, <tdevries@suse.de>
Subject: [PATCH 9/9] nvptx: Re-enable 'gcc.misc-tests/options.exp'
Date: Fri, 2 Dec 2022 13:03:15 +0100	[thread overview]
Message-ID: <20221202120315.803120-10-thomas@codesourcery.com> (raw)
In-Reply-To: <20221202120315.803120-1-thomas@codesourcery.com>

..., just conditionalize its profiling test (as done elsewhere).

        gcc/testsuite/
        * gcc.misc-tests/options.exp: Re-enable for nvptx.
---
 gcc/testsuite/gcc.misc-tests/options.exp | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/gcc/testsuite/gcc.misc-tests/options.exp b/gcc/testsuite/gcc.misc-tests/options.exp
index c939aef1f4bc..a055786ea0c1 100644
--- a/gcc/testsuite/gcc.misc-tests/options.exp
+++ b/gcc/testsuite/gcc.misc-tests/options.exp
@@ -21,12 +21,6 @@

 load_lib gcc-defs.exp

-# disable for non-profile targets explitly, rather than
-# rely on check-effective target.  We're explicitly trying to check
-# profiling works, and if it doesn't check-effective-target will
-# simply skip the tests, rather than have this test shout at us.
-if [ istarget "nvptx-*-*" ] { return 0 }
-
 # These tests don't run runtest_file_p consistently if it
 # doesn't return the same values, so disable parallelization
 # of this *.exp file.  The first parallel runtest to reach
@@ -73,7 +67,9 @@ proc check_for_all_options {language gcc_options compiler_pattern as_pattern ld_
     pass $test
 }

-check_for_all_options c {--coverage} {-fprofile-arcs -ftest-coverage} {} {-lgcov}
+if { [check_profiling_available "-fprofile-arcs"] } {
+    check_for_all_options c {--coverage} {-fprofile-arcs -ftest-coverage} {} {-lgcov}
+}

 proc get_dump_flags {} {
     set res [list]
--
2.35.1

-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  parent reply	other threads:[~2022-12-02 12:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 12:03 nvptx: Re-enable a number of test cases Thomas Schwinge
2022-12-02 12:03 ` [PATCH 1/9] nvptx: Re-enable 'gcc.c-torture/compile/20080721-1.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 2/9] nvptx: Re-enable "ptxas times out" test cases Thomas Schwinge
2022-12-02 12:03 ` [PATCH 3/9] nvptx: Re-enable test cases by removing effective target 'freestanding' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 4/9] nvptx: Re-enable all variants of 'gcc.c-torture/execute/20020529-1.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 5/9] nvptx: Re-enable 'gcc.dg/special/weak-2.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 6/9] nvptx: Re-enable all variants of 'c-c++-common/torture/complex-sign-mixed-add.c', 'c-c++-common/torture/complex-sign-mixed-sub.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 7/9] nvptx: Re-enable 'gcc.dg/torture/c99-contract-1.c' Thomas Schwinge
2022-12-02 12:03 ` [PATCH 8/9] nvptx: Re-enable "Stack alignment causes use of alloca" test cases Thomas Schwinge
2022-12-02 12:03 ` Thomas Schwinge [this message]
2022-12-20  7:56 ` [PING] nvptx: Re-enable a number of " Thomas Schwinge
2023-01-11 11:34   ` [PING^2] " Thomas Schwinge

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=20221202120315.803120-10-thomas@codesourcery.com \
    --to=thomas@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tdevries@suse.de \
    /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).