On Tue, Oct 17, 2023 at 9:51 PM Jason Merrill wrote:
>
> Ping?
OK.
Thanks,
Richard.
> On 10/3/23 17:09, Jason Merrill wrote:
> > This revision changes from using DK_PEDWARN for permerror-with-option to
> > using
> > DK_PERMERROR.
> >
> > Tested x86_64-pc-linux-gnu. OK for trunk?
> >
> > -- 8<
Ping?
On 10/3/23 17:09, Jason Merrill wrote:
This revision changes from using DK_PEDWARN for permerror-with-option to using
DK_PERMERROR.
Tested x86_64-pc-linux-gnu. OK for trunk?
-- 8< --
In the discussion of promoting some pedwarns to be errors by default, rather
than move them all into -f
On 10/4/23 03:07, Florian Weimer wrote:
* Jason Merrill:
@@ -6159,6 +6153,18 @@ errors by @option{-pedantic-errors}. For instance:
-Wwrite-strings @r{(C++11 or later)}
}
+@opindex fpermissive
+@item -fpermissive
+Downgrade some required diagnostics about nonconformant code from
+errors
* Jason Merrill:
> @@ -6159,6 +6153,18 @@ errors by @option{-pedantic-errors}. For instance:
> -Wwrite-strings @r{(C++11 or later)}
> }
>
> +@opindex fpermissive
> +@item -fpermissive
> +Downgrade some required diagnostics about nonconformant code from
> +errors to warnings. Thus, using @opt
This revision changes from using DK_PEDWARN for permerror-with-option to using
DK_PERMERROR.
Tested x86_64-pc-linux-gnu. OK for trunk?
-- 8< --
In the discussion of promoting some pedwarns to be errors by default, rather
than move them all into -fpermissive it seems to me to make sense to suppo
