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 rtl-optimization/101076] RTL Combine pass won't generate sign_extnd RTX in some senario Date: Tue, 15 Jun 2021 06:14:39 +0000 [thread overview] Message-ID: <bug-101076-4-YWgbN3itXk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101076-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101076 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-06-15 Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- What target is this for? For both x86_64 and aarch64 we have both shifts in SI mode so we don't end up with problem. We get the following RTL for aarch64 (before combine): (insn 6 3 7 2 (set (reg:SI 96) (ashift:SI (reg/v:SI 94 [ a ]) (const_int 16 [0x10]))) "t551.c":3:15 692 {*aarch64_ashl_sisd_or_int_si3} (expr_list:REG_DEAD (reg/v:SI 94 [ a ]) (nil))) (insn 7 6 12 2 (set (reg:SI 95) (ashiftrt:SI (reg:SI 96) (const_int 16 [0x10]))) "t551.c":3:22 696 {*aarch64_ashr_sisd_or_int_si3} (expr_list:REG_DEAD (reg:SI 96) (nil))) And then we get: Trying 6 -> 7: 6: r96:SI=r97:SI<<0x10 REG_DEAD r97:SI 7: r95:SI=r96:SI>>0x10 REG_DEAD r96:SI Successfully matched this instruction: (set (reg:SI 95) (sign_extend:SI (subreg:HI (reg:SI 97) 0))) In combine. I Noticed you have: r76:SI=r78:DI#0<<0x10 7: r75:SI=r76:SI>>0x10 In combine, so you have a subreg of r78, where is the subreg produced ...
next prev parent reply other threads:[~2021-06-15 6:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-15 3:37 [Bug rtl-optimization/101076] New: " wf831130 at sina dot com 2021-06-15 6:14 ` pinskia at gcc dot gnu.org [this message] 2021-06-15 6:31 ` [Bug rtl-optimization/101076] " wf831130 at sina dot com 2021-06-15 6:41 ` pinskia at gcc dot gnu.org 2021-06-15 6:53 ` wf831130 at sina dot com 2021-06-15 7:01 ` pinskia at gcc dot gnu.org 2023-06-02 5:25 ` 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-101076-4-YWgbN3itXk@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).