public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101223] [11/12 Regression] evrp produces wrong code Date: Mon, 28 Jun 2021 03:00:54 +0000 [thread overview] Message-ID: <bug-101223-4-COV8TxKPGr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101223-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101223 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |aldyh at gcc dot gnu.org, | |amacleod at redhat dot com Last reconfirmed| |2021-06-28 Ever confirmed|0 |1 Summary|[11/12 Regression] wrong |[11/12 Regression] evrp |code at -O2 and above on |produces wrong code |x86_64-linux-gnu | --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The problem is in evrp. Without evrp: # f_10 = PHI <0(3), c.0_1(4)> # g_11 = PHI <g_12(3), g_21(4)> c = f_10; ..... With VRP: <bb 6> : # g_11 = PHI <g_12(3), g_21(4)> c = 0; That is wrong. c.0_1: int VARYING _2: <unnamed-signed:1> VARYING _3: <unnamed-signed:1> VARYING _5: int [-1, 0] _6: <unnamed-signed:1> VARYING _8: int [-2147483647, 2] d.2_9: int VARYING g_11: int VARYING g_12: int VARYING g_15(D): UNDEFINED e_18: int VARYING g_21: int [-1, 0] Huh: Visiting PHI node: f_10 = PHI <0(3), c.0_1(4)> Argument #0 (3 -> 6 executable) 0: int [0, 0] Argument #1 (4 -> 6 executable) c.0_1: int [c.0_1, c.0_1] Meeting int [0, 0] and int [c.0_1, c.0_1] to int VARYING Intersecting int VARYING and int VARYING to int VARYING Visiting PHI node: g_11 = PHI <g_12(3), g_21(4)> Argument #0 (3 -> 6 executable) g_12: int [g_12, g_12] Argument #1 (4 -> 6 executable) g_21: int [-1, 0] Meeting int [g_12, g_12] and int [-1, 0] to int VARYING Intersecting int VARYING and int VARYING to int VARYING Folding PHI node: f_10 = PHI <0(3), c.0_1(4)> EVRP:hybrid: RVRP found singleton 0 Queued PHI for removal. Folds to: 0 Folding PHI node: g_11 = PHI <g_12(3), g_21(4)> recomputation attempt on edge 4->6 for g_21 : Calculated :int VARYING No folding possible evrp visiting stmt c = f_10; Folding statement: c = f_10; EVRP:hybrid: RVRP found singleton 0 Folded into: c = 0; We got int VARYING but still folded it to 0.
next prev parent reply other threads:[~2021-06-28 3:00 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-26 12:44 [Bug tree-optimization/101223] New: wrong code at -Os and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2021-06-28 2:34 ` [Bug tree-optimization/101223] [11/12 Regression] " pinskia at gcc dot gnu.org 2021-06-28 3:00 ` pinskia at gcc dot gnu.org [this message] 2021-06-28 3:03 ` [Bug tree-optimization/101223] [11/12 Regression] evrp produces wrong code pinskia at gcc dot gnu.org 2021-06-28 7:02 ` rguenth at gcc dot gnu.org 2021-06-28 7:27 ` [Bug tree-optimization/101223] [11/12 Regression] evrp produces wrong code since r11-3685-gfcae5121154d1c33 marxin at gcc dot gnu.org 2021-06-28 10:57 ` aldyh at gcc dot gnu.org 2021-06-28 10:58 ` jakub at gcc dot gnu.org 2021-06-28 10:59 ` aldyh at gcc dot gnu.org 2021-06-28 14:19 ` amacleod at redhat dot com 2021-07-02 13:03 ` rsandifo at gcc dot gnu.org 2021-07-02 13:14 ` jakub at gcc dot gnu.org 2021-07-02 13:18 ` rsandifo at gcc dot gnu.org 2021-07-02 15:35 ` cvs-commit at gcc dot gnu.org 2021-07-02 15:37 ` amacleod at redhat dot com 2021-07-02 20:31 ` [Bug tree-optimization/101223] [11 " pinskia at gcc dot gnu.org 2021-07-14 21:58 ` cvs-commit at gcc dot gnu.org 2021-07-14 22:16 ` 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-101223-4-COV8TxKPGr@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: linkBe 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).