public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52876] [x32] - Sign extend 32 to 64bit then clear upper 32bits fails O1 or higher Date: Thu, 05 Apr 2012 10:16:00 -0000 [thread overview] Message-ID: <bug-52876-4-Qdtq8Q8ugy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52876-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52876 Uros Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |52854 --- Comment #6 from Uros Bizjak <ubizjak at gmail dot com> 2012-04-05 10:16:32 UTC --- This is similar issue as PR 52854, but this time: (insn 6 3 7 2 (set (reg/f:DI 64 [ addr ]) (sign_extend:DI (subreg/u:SI (reg/v/f:DI 63 [ addr ]) 0))) pr52876.c:6 122 {*extendsidi2_rex64} (expr_list:REG_DEAD (reg/v/f:DI 63 [ addr ]) (nil))) (insn 7 6 8 2 (parallel [ (set (reg:DI 61 [ li.4 ]) (and:DI (reg/f:DI 64 [ addr ]) (const_int 4294967295 [0xffffffff]))) (clobber (reg:CC 17 flags)) ]) pr52876.c:10 377 {*anddi_1} (expr_list:REG_DEAD (reg/f:DI 64 [ addr ]) (expr_list:REG_UNUSED (reg:CC 17 flags) (nil)))) combine converts this to: Trying 6 -> 7: Successfully matched this instruction: (set (reg:DI 61 [ li.4 ]) (reg/v/f:DI 63 [ addr ])) (note 6 3 7 2 NOTE_INSN_DELETED) (insn 7 6 8 2 (set (reg:DI 61 [ li.4 ]) (reg/v/f:DI 63 [ addr ])) pr52876.c:10 62 {*movdi_internal_rex64} (expr_list:REG_DEAD (reg/v/f:DI 63 [ addr ]) (nil)))
next prev parent reply other threads:[~2012-04-05 10:16 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-05 8:17 [Bug target/52876] New: " steffen-schmidt at siemens dot com 2012-04-05 8:19 ` [Bug target/52876] " steffen-schmidt at siemens dot com 2012-04-05 8:20 ` steffen-schmidt at siemens dot com 2012-04-05 8:20 ` steffen-schmidt at siemens dot com 2012-04-05 8:21 ` steffen-schmidt at siemens dot com 2012-04-05 8:21 ` steffen-schmidt at siemens dot com 2012-04-05 10:16 ` ubizjak at gmail dot com [this message] 2012-04-05 10:17 ` ubizjak at gmail dot com 2012-04-05 13:43 ` hjl.tools at gmail dot com 2012-04-05 13:50 ` hjl.tools at gmail dot com 2012-04-05 14:31 ` hjl.tools at gmail dot com 2012-04-05 15:17 ` [Bug rtl-optimization/52876] " ubizjak at gmail dot com 2012-04-05 15:21 ` [Bug target/52876] " hjl.tools at gmail dot com 2012-04-05 15:46 ` hjl.tools at gmail dot com 2012-04-10 14:50 ` [Bug rtl-optimization/52876] " hjl.tools at gmail dot com 2012-04-11 19:32 ` hjl at gcc dot gnu.org 2013-02-07 11:50 ` steffen-schmidt at siemens dot com 2013-02-07 16:34 ` hjl.tools at gmail dot com 2024-03-26 23:34 ` 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-52876-4-Qdtq8Q8ugy@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).