This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Deprecate -frepo option.
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Martin Liška <mliska at suse dot cz>
- Cc: Nathan Sidwell <nathan at acm dot org>, Richard Biener <richard dot guenther at gmail dot com>, Jakub Jelinek <jakub at redhat dot com>, Iain Sandoe <idsandoe at googlemail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, David Edelsohn <dje dot gcc at gmail dot com>, Jan Hubicka <hubicka at ucw dot cz>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Jason Merrill <jason at redhat dot com>
- Date: Wed, 4 Sep 2019 10:22:14 +0100
- Subject: Re: [PATCH] Deprecate -frepo option.
- References: <ac43bd46-9251-c360-b92c-52831886fc4a@suse.cz> <BC1522A8-E989-448F-BB2D-7552F1111F1D@gmail.com> <884b9feb-3e71-db00-8c72-8e096bf75c1e@suse.cz> <CAH6eHdS-oVx-pSwsFwsnsH02biaLPyrhzv-8V23JtpfXa1=WBA@mail.gmail.com> <B2D95072-A88E-4BAA-9F33-E46685EDFE9A@googlemail.com> <b8d94fbd-dc73-ad66-17ca-ce34238581e3@suse.cz> <CAH6eHdTPwE+6xv7n6HMsCmH-Ei=zTLN+vmAB-51=CzytmjEJFQ@mail.gmail.com> <69a11998-93c1-d61d-ba31-ac93bcbb353a@suse.cz> <20190621115838.GX815@tucnak> <79fcb5a4-0eba-d39f-e7ca-389f371cd48c@suse.cz> <20190621141309.GY815@tucnak> <CAFiYyc3mw2hitAyp-Xfucv5sAM6TbmTyHyicGTKWGSi5znPrgA@mail.gmail.com> <140a1eb3-9652-9516-0274-19977fa3021d@suse.cz> <CAFiYyc3h-5GPtA1rNNz1q580s+6EFJ-KyDkZu+UV3XnmDbaF5g@mail.gmail.com> <c8c30610-e366-f42a-d459-a542f2455a8e@acm.org> <5c3aaf4a-b68a-f7a1-38b7-2e83182b0bc4@suse.cz> <91e9319a-6154-e252-35c2-cdcce679ea07@suse.cz>
On Wed, 4 Sep 2019 at 09:13, Martin Liška wrote:
>
> On 7/9/19 3:00 PM, Martin Liška wrote:
> > Great. Then I'm sending patch that does the functionality removal.
>
> Hi.
>
> The GCC 9.2.0 is released and the version contains a deprecation
> warning for -frepo.
>
> Is it the right time now to remove it from trunk?
If users upgrade to 9.2 in 6 months, see the new warning, and tell us
they're using the feature, will it be possible to re-enable it?
The point of the warning was to see if users complain. Three weeks
isn't a very long time to see if users are going to complain :-)