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 middle-end/107190] [aarch64] regression with optimization -fexpensive-optimizations Date: Mon, 10 Oct 2022 17:31:02 +0000 [thread overview] Message-ID: <bug-107190-4-zmxAkO5Jmu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107190-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107190 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|rtl-optimization |middle-end --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I think it is the expansion of the add with overflow causing things to be worse. (insn 16 15 17 (set (reg:DI 102 [ _17+8 ]) (const_int 0 [0])) -1 (nil)) (insn 17 16 18 (parallel [ (set (reg:CC_C 66 cc) (compare:CC_C (plus:DI (reg:DI 109 [ m ]) (reg:DI 111 [ m1 ])) (reg:DI 109 [ m ]))) (set (reg:DI 112) (plus:DI (reg:DI 109 [ m ]) (reg:DI 111 [ m1 ]))) ]) -1 (nil)) (jump_insn 18 17 19 (set (pc) (if_then_else (ltu (reg:CC_C 66 cc) (const_int 0 [0])) (label_ref 21) (pc))) -1 (int_list:REG_BR_PROB 536868 (nil))) (jump_insn 19 18 20 (set (pc) (label_ref 23)) -1 (nil)) (barrier 20 19 21) (code_label 21 20 22 3 (nil) [0 uses]) (insn 22 21 23 (set (reg:DI 102 [ _17+8 ]) (const_int 1 [0x1])) -1 (nil)) (code_label 23 22 24 2 (nil) [0 uses]) I don't see why we need to expand to a jump here rather than a cset? I think there is another bug about this already too.
next prev parent reply other threads:[~2022-10-10 17:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-09 10:33 [Bug c++/107190] New: " zhongyunde at huawei dot com 2022-10-10 16:54 ` [Bug rtl-optimization/107190] " pinskia at gcc dot gnu.org 2022-10-10 17:31 ` pinskia at gcc dot gnu.org [this message] 2023-05-19 1:22 ` [Bug middle-end/107190] " 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-107190-4-zmxAkO5Jmu@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).