public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/113597] [14 Regression] aarch64: Significant code quality regression since r14-8346-ga98d5130a6dcff Date: Thu, 25 Jan 2024 13:41:42 +0000 [thread overview] Message-ID: <bug-113597-4-9eSxTbtwXf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113597-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113597 --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- In DSE the only differences is fbt (0x7ffff51a1a50: (plus:DI (reg/v/f:DI 117 [ u ]) - (reg:DI 146 [ _44 ]))) == (address 0) + (reg:DI 146 [ _44 ]))) == (nil) fbt (0x7ffff700b3c0: (reg/f:DI 64 sfp)) == (address:DI -3) -bac false +bac true that's for (mem:BLK (reg/f:DI 64 sfp) [0 A8]) vs (mem:V4SF (plus:DI (reg/v/f:DI 117 [ u ]) (reg:DI 146 [ _44 ])) [0 MEM <__Float32x4_t> [(float * {ref-all})_42]+0 S16 A32]) from #0 0x0000000002ff3796 in scan_reads (insn_info=0x5e5b680, gen=0x5ec2338, kill=0x5ec2358) at /space/rguenther/src/gcc/gcc/dse.cc:3156 #1 0x0000000002ff39b1 in dse_step3_scan (bb=<basic_block 0x7ffff5160060 (5)>) at /space/rguenther/src/gcc/gcc/dse.cc:3238 processing (insn 62 61 64 5 (set (reg:V4SF 147 [ MEM <__Float32x4_t> [(float * {ref-all})_42] ]) (mem:V4SF (plus:DI (reg/v/f:DI 117 [ u ]) (reg:DI 146 [ _44 ])) [0 MEM <__Float32x4_t> [(float * {ref-all})_42]+0 S16 A32])) "include/arm_neon.h":12531:36 1274 {*aarch64_simd_movv4sf} (expr_list:REG_DEAD (reg:DI 146 [ _44 ]) (nil))) in this case we have _44 point to NONLOCAL only. It got arg_base_value as base value (from the MEM_EXPR and that points-to set we could eventually derive this very same base term as well). But I'll note that (mem:BLK (reg/f:DI 64 sfp) [0 A8]) is artificial, generated by DSE get_group_info via record_store on (insn 13 12 14 2 (set (mem/c:V2x16QI (reg/f:DI 119) [0 +0 S32 A128]) (unspec:V2x16QI [ (reg:V16QI 121) repeated x2 ] UNSPEC_STP)) "t.cc":12:10 discrim 1 92 {*store_pair_16} (nil)) which is figured to be const_or_frame_p () based. That notably lacks a MEM_EXPR (though the bare MEM means only base_alias_check would ever be able to disambiguate here).
next prev parent reply other threads:[~2024-01-25 13:41 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-25 10:53 [Bug rtl-optimization/113597] New: " acoplan at gcc dot gnu.org 2024-01-25 11:01 ` [Bug rtl-optimization/113597] " rguenth at gcc dot gnu.org 2024-01-25 11:01 ` rguenth at gcc dot gnu.org 2024-01-25 11:05 ` acoplan at gcc dot gnu.org 2024-01-25 11:10 ` acoplan at gcc dot gnu.org 2024-01-25 11:10 ` acoplan at gcc dot gnu.org 2024-01-25 11:16 ` pinskia at gcc dot gnu.org 2024-01-25 11:27 ` acoplan at gcc dot gnu.org 2024-01-25 11:32 ` acoplan at gcc dot gnu.org 2024-01-25 11:38 ` pinskia at gcc dot gnu.org 2024-01-25 11:40 ` acoplan at gcc dot gnu.org 2024-01-25 11:56 ` rguenth at gcc dot gnu.org 2024-01-25 13:41 ` rguenth at gcc dot gnu.org [this message] 2024-01-25 14:03 ` rguenth at gcc dot gnu.org 2024-01-29 13:56 ` rguenth at gcc dot gnu.org 2024-03-07 20:45 ` law at gcc dot gnu.org 2024-05-07 7:44 ` [Bug rtl-optimization/113597] [14/15 " rguenth 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-113597-4-9eSxTbtwXf@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).