public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r9-9780] libstdc++: Rename tests with incorrect extension
Date: Wed, 13 Oct 2021 19:42:55 +0000 (GMT)	[thread overview]
Message-ID: <20211013194255.1CD183858426@sourceware.org> (raw)

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

commit r9-9780-gb1d8d3a209f36affd2ad361ab312094fc9639f4d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Sep 17 12:25:40 2021 +0100

    libstdc++: Rename tests with incorrect extension
    
    The libstdc++ testsuite only runs .cc files, so these two old tests have
    never been run.
    
    Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/26_numerics/valarray/dr630-3.C: Moved to...
            * testsuite/26_numerics/valarray/dr630-3.cc: ...here.
            * testsuite/27_io/basic_iostream/cons/16251.C: Moved to...
            * testsuite/27_io/basic_iostream/cons/16251.cc: ...here.
    
    (cherry picked from commit 749c31b345c2a37106b57ce805ea46a6d4765e09)

Diff:
---
 libstdc++-v3/testsuite/26_numerics/valarray/{dr630-3.C => dr630-3.cc}  | 0
 libstdc++-v3/testsuite/27_io/basic_iostream/cons/{16251.C => 16251.cc} | 0
 2 files changed, 0 insertions(+), 0 deletions(-)

diff --git a/libstdc++-v3/testsuite/26_numerics/valarray/dr630-3.C b/libstdc++-v3/testsuite/26_numerics/valarray/dr630-3.cc
similarity index 100%
rename from libstdc++-v3/testsuite/26_numerics/valarray/dr630-3.C
rename to libstdc++-v3/testsuite/26_numerics/valarray/dr630-3.cc
diff --git a/libstdc++-v3/testsuite/27_io/basic_iostream/cons/16251.C b/libstdc++-v3/testsuite/27_io/basic_iostream/cons/16251.cc
similarity index 100%
rename from libstdc++-v3/testsuite/27_io/basic_iostream/cons/16251.C
rename to libstdc++-v3/testsuite/27_io/basic_iostream/cons/16251.cc


                 reply	other threads:[~2021-10-13 19:42 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=20211013194255.1CD183858426@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-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).