From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id E73343858402; Tue,  2 Nov 2021 09:08:18 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E73343858402
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103037] [11/12 Regression] Wrong code with
 -O2 since r11-6100-gd41b097350d3c5d0
Date: Tue, 02 Nov 2021 09:08:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-103037-4-fDT7p8rdU5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-103037-4@http.gcc.gnu.org/bugzilla/>
References: <bug-103037-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2021 09:08:19 -0000

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We have:
  var_3.2_4 =3D var_3;
  iftmp.1_14 =3D (int) var_3.2_4;
  var_11_lsm.14_8 =3D _7(D);

  <bb 3> [local count: 955630225]:
  # RANGE [0, 24] NONZERO 31
  # a_20 =3D PHI <a_18(10), 0(9)>
  _19 =3D MEM <short unsigned int[23]> [(short unsigned int &)&arr_4][a_20];
  if (_19 > 1)
    goto <bb 5>; [50.00%]
  else
    goto <bb 4>; [50.00%]

  <bb 4> [local count: 477815112]:
  # RANGE [0, 1] NONZERO 1
  _3 =3D (int) _19;
  if (_19 !=3D 0)
    goto <bb 5>; [20.00%]
  else
    goto <bb 6>; [80.00%]

  <bb 5> [local count: 477815112]:
  # RANGE [0, 1] NONZERO 1
  # _24 =3D PHI <_3(4), 1(3)>
  # RANGE [1, 65535] NONZERO 65535
  iftmp.1_15 =3D (int) _19;
  goto <bb 7>; [100.00%]

  <bb 6> [local count: 477815112]:

  <bb 7> [local count: 955630225]:
  # RANGE [-32768, 65535]
  # iftmp.1_10 =3D PHI <iftmp.1_15(5), iftmp.1_14(6)>
  # RANGE [0, 1] NONZERO 1
  # _25 =3D PHI <_24(5), 0(6)>
  # RANGE [-1, 1]
  _5 =3D _25 / iftmp.1_10;
and seems PRE is trying top simplify 1 / _3 and _3 / _3.  _3 has correctly
range of [0, 1] - in that bb _19 can't be anything but 0 or 1 given the
condition, but
iftmp.1_15 =3D (int) _19; isn't equivalent to that, because it is reachable=
 from
other bbs, even when it is also (int) _19.
So, does PRE need to temporarily reset_flow_sensitive_info in such cases and
restore if it didn't succeed?=