public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: "François-Xavier Coudert" <fxcoudert@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-5572] Testsuite: remove unused variables
Date: Sat, 18 Nov 2023 09:02:31 +0000 (GMT)	[thread overview]
Message-ID: <20231118090231.6DAF63858409@sourceware.org> (raw)

https://gcc.gnu.org/g:f76d47e6bcd2c196bb525eead7e01688e1a732a9

commit r14-5572-gf76d47e6bcd2c196bb525eead7e01688e1a732a9
Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
Date:   Sat Nov 18 10:01:14 2023 +0100

    Testsuite: remove unused variables
    
    Missing from earlier commit, which removed the only use of those two
    variables.
    
    gcc/testsuite/ChangeLog:
    
            * gfortran.dg/coarray/caf.exp: Remove unused variable.
            * gfortran.dg/dg.exp: Remove unused variable.

Diff:
---
 gcc/testsuite/gfortran.dg/coarray/caf.exp | 1 -
 gcc/testsuite/gfortran.dg/dg.exp          | 1 -
 2 files changed, 2 deletions(-)

diff --git a/gcc/testsuite/gfortran.dg/coarray/caf.exp b/gcc/testsuite/gfortran.dg/coarray/caf.exp
index fab8238a0d5..c626265e7b2 100644
--- a/gcc/testsuite/gfortran.dg/coarray/caf.exp
+++ b/gcc/testsuite/gfortran.dg/coarray/caf.exp
@@ -80,7 +80,6 @@ if [check_effective_target_libatomic_available] {
 	    set maybe_atomic_lib "[atomic_link_flags [get_multilibs]]"
 	}
     }
-    set t [get_multilibs]
 }
 
 # Main loop.
diff --git a/gcc/testsuite/gfortran.dg/dg.exp b/gcc/testsuite/gfortran.dg/dg.exp
index 22f2ffb405f..253c0f5ec6a 100644
--- a/gcc/testsuite/gfortran.dg/dg.exp
+++ b/gcc/testsuite/gfortran.dg/dg.exp
@@ -67,7 +67,6 @@ if [check_effective_target_libatomic_available] {
     } else {
         set maybe_atomic_lib ""
     }
-  set t [get_multilibs]
 }
 
 set all_flags $DEFAULT_FFLAGS

                 reply	other threads:[~2023-11-18  9:02 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=20231118090231.6DAF63858409@sourceware.org \
    --to=fxcoudert@gcc.gnu.org \
    --cc=gcc-cvs@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: 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).