From: Alexandre Oliva <oliva@gnu.org>
To: Martin Jambor <mjambor@suse.cz>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Mass rename of C++ .c files to .cc suffix?
Date: Fri, 07 Jan 2022 15:33:54 -0300 [thread overview]
Message-ID: <or4k6fjsz1.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <ri6mtk7vo41.fsf@suse.cz> (Martin Jambor's message of "Fri, 07 Jan 2022 11:25:50 +0100")
On Jan 7, 2022, Martin Jambor <mjambor@suse.cz> wrote:
> Would anyone be terribly against mass renaming all *.c files (that are
> actually C++ files) within the gcc subdirectory to ones with .cc suffix?
I wouldn't mind that.
> (Any important caveats I might have missed?)
Having recently renamed a .c source to .cc in a development branch, one
annoying issue that came up was that dependency tracking in build trees
couldn't recover from the renaming on its own: it kept on insisting that
the previously-existing .c file was missing, instead of picking up the
.cc. This could be a problem for hands-off CI testers, besides the
slight annoyance of having to wipe out the build tree, or at least hunt
down and remove dep-tracking files.
It's no biggie, I'm not sure there's some change to the build machinery
we could make ahead of time to alleviate this, but it should probably be
mentioned in the announcement of the change if/when it goes in.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-01-07 18:34 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 10:25 Martin Jambor
2022-01-07 10:33 ` Richard Sandiford
2022-01-07 10:44 ` Andrew Pinski
2022-01-07 10:51 ` Jonathan Wakely
2022-01-07 10:51 ` Jakub Jelinek
2022-01-07 11:05 ` Jonathan Wakely
2022-01-07 12:55 ` Martin Liška
2022-01-07 14:42 ` Iain Sandoe
2022-01-07 14:49 ` Jeff Law
2022-01-07 15:45 ` Jeff Law
2022-01-07 15:59 ` David Malcolm
2022-01-07 17:31 ` Jonathan Wakely
2022-01-10 9:11 ` Martin Liška
2022-01-07 18:33 ` Alexandre Oliva [this message]
2022-01-07 19:01 ` Jakub Jelinek
2022-01-11 12:56 ` [PATCH] Mass rename of C++ .c files to .cc suffix Martin Liška
2022-01-11 15:48 ` Toon Moene
2022-01-11 15:50 ` Martin Liška
2022-01-11 15:56 ` Jakub Jelinek
2022-01-11 16:03 ` Martin Liška
2022-01-11 16:16 ` Jakub Jelinek
2022-01-12 8:58 ` Martin Liška
2022-01-12 15:54 ` [PATCH] git-backport: support renamed .cc files in commit message Martin Liška
2022-01-14 7:44 ` Bernhard Reutner-Fischer
2022-01-14 15:26 ` Martin Liška
2022-01-17 21:26 ` Martin Liška
2022-01-18 19:10 ` Harald Anlauf
2022-01-19 8:07 ` Martin Liška
2022-01-11 18:00 ` [PATCH] Mass rename of C++ .c files to .cc suffix Harald Anlauf
2022-01-11 18:00 ` Harald Anlauf
2022-01-11 18:23 ` Jonathan Wakely
2022-01-11 18:36 ` Jakub Jelinek
2022-01-13 11:01 ` [ANNOUNCEMENT] Mass rename of C++ .c files to .cc suffix is going to happen on Jan 17 evening UTC TZ Martin Liška
2022-01-17 21:41 ` Martin Liška
2022-01-18 8:36 ` Eric Botcazou
2022-01-18 8:39 ` Martin Liška
2022-01-18 8:46 ` Eric Botcazou
2022-01-18 8:53 ` Richard Biener
2022-01-18 9:08 ` Martin Liška
2022-01-18 9:13 ` Jakub Jelinek
2022-01-18 9:43 ` Martin Liška
2022-01-18 13:10 ` Richard Earnshaw
2022-01-18 13:16 ` Martin Liška
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=or4k6fjsz1.fsf@lxoliva.fsfla.org \
--to=oliva@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mjambor@suse.cz \
/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).