public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94675] [9/10 regression] -Warray-bounds false positive with -O2
Date: Tue, 21 Apr 2020 07:58:54 +0000	[thread overview]
Message-ID: <bug-94675-4-mW9C3T4dbV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94675-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94675

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |10.0, 9.3.0
            Summary|[9 regression]              |[9/10 regression]
                   |-Warray-bounds false        |-Warray-bounds false
                   |positive with -O2           |positive with -O2
      Known to work|                            |8.4.0

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
In the original testcase I clearly see some missed optimizations, notably
the failure to "thread"

  if (_12 > 6)
    goto <bb 4>; [50.00%]
  else
    goto <bb 3>; [50.00%]

  <bb 3> [local count: 536870913]:

  <bb 4> [local count: 1073741824]:
  # iftmp.2_13 = PHI <0(3), 1(2)>
  _14 = (_Bool) iftmp.2_13;
  if (_14 != 0)
    goto <bb 5>; [90.00%]
  else
    goto <bb 6>; [10.00%]

and as you say simplification of a pointer comparison

  _6 = &c + _2;
  _11 = _6 - &c;
  _12 = (long unsigned int) _11;
  if (_12 > 6)

we're doing the simplification only late because forwprop depends on FRE
and FRE doesn't apply match.pd rules unrestricted like forwprop does.
Not doing any DCE before VRP probably doesn't help either (DCE
would have removed the offending statement).

  parent reply	other threads:[~2020-04-21  7:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 19:42 [Bug tree-optimization/94675] New: [9 " chantry.xavier at gmail dot com
2020-04-20 22:16 ` [Bug tree-optimization/94675] " msebor at gcc dot gnu.org
2020-04-21  6:51 ` chantry.xavier at gmail dot com
2020-04-21  7:04 ` marxin at gcc dot gnu.org
2020-04-21  7:46 ` rguenth at gcc dot gnu.org
2020-04-21  7:58 ` rguenth at gcc dot gnu.org [this message]
2020-04-21  7:59 ` [Bug tree-optimization/94675] [9/10 " jakub at gcc dot gnu.org
2020-04-21  8:06 ` [Bug tree-optimization/94675] [9/10 regression] -Warray-bounds false positive with -O2 since r9-1948 jakub at gcc dot gnu.org
2020-04-21 14:03 ` law at redhat dot com
2020-04-21 14:18 ` rguenther at suse dot de
2020-04-21 14:43 ` law at redhat dot com
2020-04-21 14:57 ` rguenther at suse dot de
2020-04-21 14:58 ` msebor at gcc dot gnu.org
2020-04-21 19:14 ` law at redhat dot com
2020-04-21 19:16 ` law at redhat dot com
2020-04-21 20:10 ` law at redhat dot com
2020-04-21 21:00 ` msebor at gcc dot gnu.org
2020-04-22  6:34 ` rguenther at suse dot de
2020-04-24  7:48 ` chantry.xavier at gmail dot com
2020-04-24 15:16 ` msebor at gcc dot gnu.org
2020-04-30 13:12 ` chantry.xavier at gmail dot com
2021-06-01  8:17 ` [Bug tree-optimization/94675] [9/10/11/12 " rguenth at gcc dot gnu.org
2021-09-06 11:25 ` pinskia at gcc dot gnu.org
2022-03-16 11:09 ` chantry.xavier at gmail dot com
2022-03-16 13:24 ` rguenth at gcc dot gnu.org
2022-05-27  9:42 ` [Bug tree-optimization/94675] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2023-05-14 21:25 ` [Bug tree-optimization/94675] [10/11/12/13/14 " pinskia at gcc dot gnu.org
2023-07-07 10:37 ` [Bug tree-optimization/94675] [11/12/13/14 " rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94675-4-mW9C3T4dbV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).