public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108953] inefficient codegen for trivial equality Date: Mon, 27 Feb 2023 17:11:47 +0000 [thread overview] Message-ID: <bug-108953-4-bBTMA9VKWM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108953-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108953 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |tree-optimization CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I don't think there is anything the C++ FE should do here, user can write it like that by hand too: bool check(C const& lhs, C const& rhs) { if (lhs.a != rhs.a) return false; if (lhs.b != rhs.b) return false; if (lhs.c != rhs.c) return false; if (lhs.d != rhs.d) return false; if (lhs.e != rhs.e) return false; if (lhs.f != rhs.f) return false; if (lhs.g != rhs.g) return false; return true; } etc., so we should pattern match this somewhere during GIMPLE opts. The memcmp issue is a RTL issue (so I think we want actually two bugs), at GIMPLE level it is optimized into: _1 = __builtin_memcmp_eq (lhs_3(D), rhs_4(D), 12); _5 = _1 == 0; return _5; which is I think what we want. The reason for doing conditional branch after each comparison is targetm.compare_by_pieces_branch_ratio (DImode) tells it not to batch more than one. Not really sure if we should override it to something else and on which targets. The reason for the weird mov eax, 1 test eax, eax sete al instead of xor eax, eax and xor eax, eax test eax, eax sete al instead of mov eax, 1 is that the epilogue is threaded only too late where the constant propagation through it isn't possible.
next prev parent reply other threads:[~2023-02-27 17:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 16:29 [Bug c++/108953] New: " barry.revzin at gmail dot com 2023-02-27 16:38 ` [Bug c++/108953] " pinskia at gcc dot gnu.org 2023-02-27 17:11 ` jakub at gcc dot gnu.org [this message] 2023-02-28 10:44 ` [Bug tree-optimization/108953] " rguenth at gcc dot gnu.org 2023-03-02 15:05 ` jakub at gcc dot gnu.org 2023-06-23 22:59 ` pinskia at gcc dot gnu.org 2023-07-13 18:15 ` [Bug c++/108953] " pinskia 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-108953-4-bBTMA9VKWM@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).