| Summary: | [11/12/13/14 Regression] gcc.dg/Wstrict-overflow-18.c gcc.dg/Wstrict-overflow-7.c gcc.dg/pragma-diag-3.c | ||
|---|---|---|---|
| Product: | gcc | Reporter: | Marc Glisse <glisse> |
| Component: | tree-optimization | Assignee: | Not yet assigned to anyone <unassigned> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | david, dimhen, egallager, gabravier |
| Priority: | P4 | Keywords: | diagnostic, xfail |
| Version: | 8.0 | ||
| Target Milestone: | 11.5 | ||
| Host: | Target: | ||
| Build: | Known to work: | ||
| Known to fail: | Last reconfirmed: | 2017-09-29 00:00:00 | |
|
Description
Marc Glisse
2017-04-24 21:16:53 UTC
(In reply to Marc Glisse from comment #0) > I will soon commit a patch that breaks (and xfails) > gcc.dg/Wstrict-overflow-18.c, see > https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00986.html. As asked by > Martin, this PR is here to track this regression. > > Most likely this will be solved by Richard (or someone else) killing > -Wstrict-overflow. Confirmed, although my preferred fix would be to keep and improve -Wstrict-overflow instead of killing it completely. https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=253642 2 more testcases got xfailed: gcc.dg/Wstrict-overflow-7.c and gcc.dg/pragma-diag-3.c. Some possibilities: - add the warning in match.pd: users keep complaining about those strict-overflow warnings, so we would have to take it out of Wall. - add the warning in match.pd, restricted to GENERIC: that gets us close to the gcc-7 situation. - reimplement the warning in the front-end. In general, telling users that we simplified x+1<x to false is an optimization note, not a valid warning (it happens in perfectly fine code where we don't have any easy workaround). However, when the user literally writes x+1<x, that does deserve a warning. This would likely miss a lot of errors we currently notice, but that's unavoidable. GCC 8.1 has been released. GCC 8.2 has been released. GCC 8.3 has been released. GCC 8.4.0 has been released, adjusting target milestone. GCC 8 branch is being closed. GCC 9.4 is being released, retargeting bugs to GCC 9.5. *** Bug 100702 has been marked as a duplicate of this bug. *** GCC 9 branch is being closed GCC 10.4 is being released, retargeting bugs to GCC 10.5. GCC 10 branch is being closed. |