On Thu, Sep 24, 2020 at 9:48 AM H.J. Lu <hjl.to...@gmail.com> wrote: > > On Wed, Sep 16, 2020 at 4:47 AM Jakub Jelinek <ja...@redhat.com> wrote: > > > > On Wed, Sep 16, 2020 at 12:34:50PM +0100, Richard Sandiford wrote: > > > Jakub Jelinek via Gcc-patches <gcc-patches@gcc.gnu.org> writes: > > > > On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches wrote: > > > >> Something like this for GCC 8 and 9. > > > > > > > > Guess my preference would be to do this everywhere and then let's > > > > discuss if > > > > we change the warning into error there or keep it being deprecated. > > > > > > Agreed FWIW. On turning it into an error: I think it might be better > > > to wait a bit longer if we can. > > > > Ok. The patch is ok for trunk and affected release branches after a week. > > > > I cherry-picked it to GCC 9 and 10 branches. GCC 8 needs some > changes. I am enclosing the backported patch for GCC 8. I will check > it in if there are no regressions on Linux/x86-64. >
No regression. I am checking it into GCC 8 branch. -- H.J.
