public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Richard Biener <richard.guenther@gmail.com>,
	Eric Botcazou <botcazou@adacore.com>,
	GCC Mailing List <gcc@gcc.gnu.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ANNOUNCEMENT] Mass rename of C++ .c files to .cc suffix is going to happen on Jan 17 evening UTC TZ
Date: Tue, 18 Jan 2022 10:13:56 +0100	[thread overview]
Message-ID: <20220118091356.GU2646553@tucnak> (raw)
In-Reply-To: <8eb04a0d-197c-39fa-d03c-4f1a7f89501a@suse.cz>

On Tue, Jan 18, 2022 at 10:08:20AM +0100, Martin Liška wrote:
> On 1/18/22 09:53, Richard Biener wrote:
> > Technically all release managers are also global reviewers, but I
> > agree the speciality
> > of the Ada setup (esp. the runtime being in gcc/) could have been anticipated.
> 
> Yeah, I thought that building Ada FE is enough for testing effort, sorry.
> 
> I would like to install the following 2 patches that revert the changes.
> After the change we're going to have:
> 
> marxin@marxinbox:~/Programming/gcc/gcc/ada> find . -name '*.cc'
> ./gcc-interface/targtyps.cc
> ./gcc-interface/decl.cc
> ./gcc-interface/cuintp.cc
> ./gcc-interface/trans.cc
> ./gcc-interface/misc.cc
> ./gcc-interface/utils2.cc
> ./gcc-interface/utils.cc
> 
> So far I've just make check-ada and there are no failures.
> 
> May I install the patch?

LGTM.

> From ddbf347224c27b7ecf41c546081db13cde136cf3 Mon Sep 17 00:00:00 2001
> From: Martin Liska <mliska@suse.cz>
> Date: Tue, 18 Jan 2022 10:02:47 +0100
> Subject: [PATCH 2/2] Ada: Revert filename changes in comments.
> 
> gcc/ada/ChangeLog:
> 
> 	* adaint.c: Revert filename changes in comments.
> 	* ctrl_c.c (dummy_handler): Likewise.
> 	* gsocket.h: Likewise.
> 	* init.c (__gnat_error_handler): Likewise.
> 	* libgnarl/s-intman.ads: Likewise.
> 	* libgnarl/s-osinte__android.ads: Likewise.
> 	* libgnarl/s-osinte__darwin.ads: Likewise.
> 	* libgnarl/s-osinte__hpux.ads: Likewise.
> 	* libgnarl/s-osinte__linux.ads: Likewise.
> 	* libgnarl/s-osinte__qnx.ads: Likewise.
> 	* libgnarl/s-taskin.ads: Likewise.
> 	* rtfinal.c: Likewise.

> gcc/ada/ChangeLog:
> 
> 	* Make-generated.in: Revert renaming changes.
> 	* Makefile.rtl: Likewise.
> 	* adadecode.cc: Moved to...
> 	* adadecode.c: ...here.
> 	* affinity.cc: Moved to...
> 	* affinity.c: ...here.
> 	* argv-lynxos178-raven-cert.cc: Moved to...
> 	* argv-lynxos178-raven-cert.c: ...here.
> 	* argv.cc: Moved to...
> 	* argv.c: ...here.
> 	* aux-io.cc: Moved to...
> 	* aux-io.c: ...here.
> 	* cio.cc: Moved to...
> 	* cio.c: ...here.
> 	* cstreams.cc: Moved to...
> 	* cstreams.c: ...here.
> 	* env.cc: Moved to...
> 	* env.c: ...here.
> 	* exit.cc: Moved to...
> 	* exit.c: ...here.
> 	* expect.cc: Moved to...
> 	* expect.c: ...here.
> 	* final.cc: Moved to...
> 	* final.c: ...here.
> 	* gcc-interface/Makefile.in:
> 	* init.cc: Moved to...
> 	* init.c: ...here.
> 	* initialize.cc: Moved to...
> 	* initialize.c: ...here.
> 	* libgnarl/thread.cc: Moved to...
> 	* libgnarl/thread.c: ...here.
> 	* link.cc: Moved to...
> 	* link.c: ...here.
> 	* locales.cc: Moved to...
> 	* locales.c: ...here.
> 	* mkdir.cc: Moved to...
> 	* mkdir.c: ...here.
> 	* raise.cc: Moved to...
> 	* raise.c: ...here.
> 	* rtfinal.cc: Moved to...
> 	* rtfinal.c: ...here.
> 	* rtinit.cc: Moved to...
> 	* rtinit.c: ...here.
> 	* s-oscons-tmplt.c (CND):
> 	* seh_init.cc: Moved to...
> 	* seh_init.c: ...here.
> 	* sigtramp-armdroid.cc: Moved to...
> 	* sigtramp-armdroid.c: ...here.
> 	* sigtramp-ios.cc: Moved to...
> 	* sigtramp-ios.c: ...here.
> 	* sigtramp-qnx.cc: Moved to...
> 	* sigtramp-qnx.c: ...here.
> 	* sigtramp-vxworks.cc: Moved to...
> 	* sigtramp-vxworks.c: ...here.
> 	* socket.cc: Moved to...
> 	* socket.c: ...here.
> 	* tracebak.cc: Moved to...
> 	* tracebak.c: ...here.
> 	* version.cc: Moved to...
> 	* version.c: ...here.
> 	* vx_stack_info.cc: Moved to...
> 	* vx_stack_info.c: ...here.

	Jakub


  reply	other threads:[~2022-01-18  9:14 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 10:25 Mass rename of C++ .c files to .cc suffix? 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
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 [this message]
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=20220118091356.GU2646553@tucnak \
    --to=jakub@redhat.com \
    --cc=botcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@gmail.com \
    /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).