public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at bigpond dot net dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/21017] ppc 64bit target not using rlwinm Date: Tue, 06 Sep 2005 00:37:00 -0000 [thread overview] Message-ID: <20050906003732.5310.qmail@sourceware.org> (raw) In-Reply-To: <20050414013914.21017.anton@samba.org> ------- Additional Comments From amodra at bigpond dot net dot au 2005-09-06 00:37 ------- Yes, we get (ior:SI (lshiftrt:SI (subreg:SI (reg/v:DI 119 [ x ]) 4) (const_int 16 [0x10])) (subreg:SI (ashift:DI (reg/v:DI 119 [ x ]) (const_int 16 [0x10])) 4)) which doesn't match the test in simplify_logical to simplify to a rotate. The second operand of ior has been "simplified" by simplify_shift_const from (ashift:SI (subreg:SI (reg/v:DI 119 [ x ]) 4) (const_int 16 [0x10])), which, if it was left that way, would allow a match. I think simplify_shift_const is OK in what it's doing, ie. it is a useful optimisation in other cases, so I'll see about matching the subreg pattern in simplify_logical. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21017
next prev parent reply other threads:[~2005-09-06 0:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-14 1:39 [Bug c/21017] New: " anton at samba dot org 2005-04-14 14:13 ` [Bug target/21017] " pinskia at gcc dot gnu dot org 2005-04-14 16:26 ` pinskia at gcc dot gnu dot org 2005-04-14 19:41 ` pinskia at gcc dot gnu dot org 2005-09-06 0:28 ` amodra at bigpond dot net dot au 2005-09-06 0:37 ` amodra at bigpond dot net dot au [this message] 2005-09-06 1:36 ` amodra at bigpond dot net dot au [not found] <bug-21017-8090@http.gcc.gnu.org/bugzilla/> 2005-12-02 6:25 ` amodra at gcc dot gnu dot org 2005-12-02 8:54 ` amodra at bigpond dot net dot au 2005-12-02 8:54 ` amodra at gcc dot gnu dot org 2005-12-02 14:02 ` pinskia at gcc dot gnu dot 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=20050906003732.5310.qmail@sourceware.org \ --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).