public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98026] optimization dependant on condition order
Date: Wed, 12 Jan 2022 19:34:35 +0000	[thread overview]
Message-ID: <bug-98026-4-eG4c1rFfGS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98026-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Macleod <amacleod at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amacleod at redhat dot com

--- Comment #3 from Andrew Macleod <amacleod at redhat dot com> ---
Although we are now adding relations for these expressions, onc extension we
have not gotten to apply ranges of relations. ie:


    <bb 2> :
    _1 = j_5(D) > i_6(D);
    _2 = i_6(D) > 100;
    _3 = _1 | _2;
    if (_3 != 0)
      goto <bb 3>; [INV]
    else
      goto <bb 4>; [INV]

2->3  (T) _3 :  bool [1, 1]
2->4  (F) _1 :  bool [0, 0]
2->4  (F) _2 :  bool [0, 0]
2->4  (F) _3 :  bool [0, 0]
2->4  (F) i_6(D) :      int [-INF, 100]

Relational : (j_5(D) <= i_6(D))
    <bb 4> :
    if (j_5(D) > 100)
      goto <bb 5>; [INV]
    else
      goto <bb 6>; [INV]

4->5  (T) j_5(D) :      int [101, +INF]
4->6  (F) j_5(D) :      int [-INF, 100]

We know that j_5 is <= i_6 on the edge 2->4, but we do not apply any known
range of i_6 to j_5.

We do transitive between symbolics, ie (j < x &&  x < y means j < y)
We do not yet do that with a range as this requires. ie:
  j_5 <= i_6,  i_6 <= 100  means j <= 100

This will be an enhancement for the next release.

  parent reply	other threads:[~2022-01-12 19:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 10:04 [Bug tree-optimization/98026] New: " denis.campredon at gmail dot com
2020-11-27 10:52 ` [Bug tree-optimization/98026] " rguenth at gcc dot gnu.org
2021-07-19  4:17 ` pinskia at gcc dot gnu.org
2022-01-12 19:34 ` amacleod at redhat dot com [this message]
2022-01-28 23:15 ` amacleod at redhat dot com
2022-01-28 23:18 ` amacleod at redhat dot com

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-98026-4-eG4c1rFfGS@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).