public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/104023] Bulk rename of C++ test files to one filename extension ? Date: Fri, 14 Jan 2022 09:52:17 +0000 [thread overview] Message-ID: <bug-104023-4-lVl0THAzyh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104023-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104023 --- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- Oh no. We usually use .cpp/.cc extension as an additional file that is intentionally skipped by a glob pattern: $ head g++.target/i386/mv12.C ... // { dg-additional-sources "mv12-aux.cc" } or: gcc/testsuite/g++.dg/asan/asan_test.C:#include "asan_str_test.cc"
next prev parent reply other threads:[~2022-01-14 9:52 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 8:06 [Bug testsuite/104023] New: " dcb314 at hotmail dot com 2022-01-14 8:15 ` [Bug testsuite/104023] " pinskia at gcc dot gnu.org 2022-01-14 8:21 ` rguenth at gcc dot gnu.org 2022-01-14 9:35 ` marxin at gcc dot gnu.org 2022-01-14 9:52 ` marxin at gcc dot gnu.org [this message] 2022-01-14 14:25 ` marxin at gcc dot gnu.org 2022-01-14 14:35 ` jakub at gcc dot gnu.org 2022-01-14 14:37 ` jakub at gcc dot gnu.org 2022-01-14 14:41 ` marxin at gcc dot gnu.org 2022-01-24 13:32 ` marxin at gcc dot gnu.org
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=bug-104023-4-lVl0THAzyh@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).