public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110170] Sub-optimal conditional jumps in conditional-swap with floating point Date: Mon, 12 Jun 2023 02:17:19 +0000 [thread overview] Message-ID: <bug-110170-4-Y2IKE6PfUk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110170-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110170 --- Comment #8 from Hongtao.liu <crazylht at gmail dot com> --- ix86_expand_sse_fp_minmax failed since rtx_equal_p (cmp_op0, if_true) is false, 249(reg:DF 86 [ _1 ]) (if_true) 250(reg:DF 83 [ _2 ]) (if_false) 251(reg:DF 82 [ _1 ]) (cmp0_op0) 252(reg:DF 83 [ _2 ]) (cmp1_op1) but here if_true is just a copy from cmp_op0 but with different REGNO, rtx_equal_p seems too conservative here. 85(code_label 26 13 17 3 4 (nil) [1 uses]) 86(note 17 26 5 3 [bb 3] NOTE_INSN_BASIC_BLOCK) 87(insn 5 17 6 3 (set (reg:DF 86 [ _1 ]) 88 (reg:DF 82 [ _1 ])) "test.C":3:20 153 {*movdf_internal} 89 (expr_list:REG_DEAD (reg:DF 82 [ _1 ]) 90 (nil))) 91(insn 6 5 7 3 (set (reg:DF 82 [ _1 ]) 92 (reg:DF 83 [ _2 ])) "test.C":4:14 discrim 1 153 {*movdf_internal} 93 (expr_list:REG_DEAD (reg:DF 83 [ _2 ]) 94 (nil))) 95(insn 7 6 18 3 (set (reg:DF 83 [ _2 ]) 96 (reg:DF 86 [ _1 ])) "test.C":3:20 discrim 1 153 {*movdf_internal} 97 (expr_list:REG_DEAD (reg:DF 86 [ _1 ]) 98 (nil))) 3812 if (rtx_equal_p (cmp_op0, if_true) && rtx_equal_p (cmp_op1, if_false)) 3813 is_min = true; 3814 else if (rtx_equal_p (cmp_op1, if_true) && rtx_equal_p (cmp_op0, if_false)) 3815 is_min = false; 3816 else 3817=> return false;
next prev parent reply other threads:[~2023-06-12 2:17 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-08 11:31 [Bug tree-optimization/110170] New: " antoshkka at gmail dot com 2023-06-08 11:34 ` [Bug tree-optimization/110170] " pinskia at gcc dot gnu.org 2023-06-08 11:57 ` [Bug target/110170] " antoshkka at gmail dot com 2023-06-08 13:32 ` pinskia at gcc dot gnu.org 2023-06-08 19:40 ` pinskia at gcc dot gnu.org 2023-06-09 5:38 ` crazylht at gmail dot com 2023-06-09 6:40 ` crazylht at gmail dot com 2023-06-09 7:01 ` crazylht at gmail dot com 2023-06-09 7:03 ` rguenth at gcc dot gnu.org 2023-06-12 2:17 ` crazylht at gmail dot com [this message] 2023-06-12 9:09 ` crazylht at gmail dot com 2023-07-04 5:46 ` crazylht at gmail dot com 2023-07-06 5:54 ` cvs-commit at gcc dot gnu.org 2023-07-10 1:06 ` cvs-commit at gcc dot gnu.org 2023-07-11 9:51 ` antoshkka at gmail dot com 2023-07-11 13:23 ` crazylht at gmail dot com 2023-07-11 13:57 ` cvs-commit at gcc dot gnu.org 2023-07-18 10:28 ` rguenth at gcc dot gnu.org 2023-07-18 10:33 ` crazylht at gmail dot com 2023-07-18 13:48 ` rguenth at gcc dot gnu.org 2023-07-21 8:18 ` rguenth at gcc dot gnu.org 2023-10-17 6:31 ` cvs-commit at gcc dot gnu.org 2023-10-17 11:14 ` cvs-commit at gcc dot gnu.org 2023-10-26 5:30 ` cvs-commit 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-110170-4-Y2IKE6PfUk@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).