public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/104023] New: Bulk rename of C++ test files to one filename extension ? Date: Fri, 14 Jan 2022 08:06:49 +0000 [thread overview] Message-ID: <bug-104023-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104023 Bug ID: 104023 Summary: Bulk rename of C++ test files to one filename extension ? Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- I notice the following in the testsuite: [/home/dcb/gcc/trunk.git/gcc/testsuite] $ find . -name \*.C -print | wc -l 18461 [/home/dcb/gcc/trunk.git/gcc/testsuite] $ find . -name \*.cc -print | wc -l 168 [/home/dcb/gcc/trunk.git/gcc/testsuite] $ find . -name \*.cpp -print | wc -l 23 [/home/dcb/gcc/trunk.git/gcc/testsuite] $ find . -name \*.cxx -print | wc -l 0 [/home/dcb/gcc/trunk.git/gcc/testsuite] $ Would it be a good idea to pick one filename extension for C++ testsuite files and stick to it ? Maybe moving to *.C would be cheap, but I notice that the main parts of the compiler are moving to using *.cc, implying that over 18,000 files might have to be moved to *.cc Just an idea. Given the amount of work involved, it might not be worth it.
next reply other threads:[~2022-01-14 8:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 8:06 dcb314 at hotmail dot com [this message] 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 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@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).