On Thu, Sep 5, 2019 at 1:02 PM Nathan Sidwell <nat...@acm.org> wrote: > > On 9/5/19 6:03 AM, Martin Liška wrote: > > On 9/5/19 12:01 PM, Richard Biener wrote: > >> On Wed, Sep 4, 2019 at 2:57 PM Nathan Sidwell <nat...@acm.org> wrote: > >>> > >>> On 9/4/19 7:20 AM, Martin Liška wrote: > >>>> On 9/4/19 11:22 AM, Jonathan Wakely wrote: > >>> > >>> > >>>>> 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 :-) > >>>>> > >>>> > >>>> I see :) That said, I'm going to install the patch close to the end > >>>> of stage1. > >>> > >>> I think it'd be ok to install it during stage3 (perhaps early feb?). > >>> More chance of people speaking up. > >> > >> I just checked and trunk doesn't spit out a warning for me so this > >> needs people to use 9.2+ to notice. > > > > Yep, it's intentional. Only GCC 9 branch prints the warning: > > > > $ gcc-9 -frepo main.cpp > > cc1plus: warning: ‘-frepo’ is deprecated and will be removed in a future > > release [-Wdeprecated] > > > > As we plan to remove it for trunk, it does not make sense to print the > > warning for trunk. > > IMHO it very much makes sense for trunk to warn. > > old-gcc: deprecated > trunk: not deprectated > conclusion: it is no longer deprecated
Once we remove -frepo it will be an option we simply ignore - correct? Then people won't notice it isn't used anymore (unless it fixes the build for them...). OTOH we figured -frepo is broken beyond repair so unless somebody steps up to actually _fix_ its issues I'm not sure what we should do when some people come around and say they use the option? So, let's just remove it now? Richard. > nathan > > -- > Nathan Sidwell
