This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Remove -Wunsafe-loop-optimizations option (PR middle-end/86095)
- From: NightStrike <nightstrike at gmail dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Richard Biener <rguenther at suse dot de>, "Bin.Cheng" <amker dot cheng at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 25 Jun 2018 13:04:12 -0400
- Subject: Re: [PATCH] Remove -Wunsafe-loop-optimizations option (PR middle-end/86095)
- References: <20180615190805.GF7166@tucnak>
On Fri, Jun 15, 2018 at 3:08 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> Hi!
>
> As mentioned in the PR, all traces of this warning option except these
> were removed earlier, so the warning option does nothing.
This is unfortunate. As noted here:
https://gcc.gnu.org/ml/gcc-patches/2016-07/msg01057.html
The warning is (or, it used to be) good at finding code areas to
rewrite, and it's MUCH easier to use than the giant walls of text from
-fopt-info. Is it possible to recreate this functionality in some
other way (or has that already been done, and I missed it)?