public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64905] unsigned short is loaded with 4-byte load (movl) Date: Mon, 02 Feb 2015 18:55:00 -0000 [thread overview] Message-ID: <bug-64905-4-aSPmCHvmuZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64905-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64905 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-02-02 CC| |ubizjak at gmail dot com Component|translation |target Target Milestone|--- |5.0 Ever confirmed|0 |1 --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- aligned_operand has if (MEM_ALIGN (op) >= 32) return true; op = XEXP (op, 0); /* Pushes and pops are only valid on the stack pointer. */ if (GET_CODE (op) == PRE_DEC || GET_CODE (op) == POST_INC) return true; /* Decode the address. */ ok = ix86_decompose_address (op, &parts); gcc_assert (ok); if (parts.base && GET_CODE (parts.base) == SUBREG) parts.base = SUBREG_REG (parts.base); if (parts.index && GET_CODE (parts.index) == SUBREG) parts.index = SUBREG_REG (parts.index); /* Look for some component that isn't known to be aligned. */ if (parts.index) { if (REGNO_POINTER_ALIGN (REGNO (parts.index)) * parts.scale < 32) return false; } if (parts.base) { if (REGNO_POINTER_ALIGN (REGNO (parts.base)) < 32) return false; } if (parts.disp) { if (!CONST_INT_P (parts.disp) || (INTVAL (parts.disp) & 3)) return false; } /* Didn't find one -- this must be an aligned address. */ return true; It returns true for (mem:HI (reg/f:DI 6 bp [orig:90 *a_p_2(D) ] [90]) [2 *_3+0 S2 A16]) Why do we need to decompose address when we have MEM_ALIGN (op)?
next prev parent reply other threads:[~2015-02-02 18:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-02 18:03 [Bug translation/64905] New: " r.ayrapetyan at samsung dot com 2015-02-02 18:55 ` hjl.tools at gmail dot com [this message] 2015-02-02 18:59 ` [Bug target/64905] " hjl.tools at gmail dot com 2015-02-02 21:40 ` hjl.tools at gmail dot com 2015-02-04 13:55 ` [Bug rtl-optimization/64905] " ubizjak at gmail dot com 2015-02-04 16:07 ` hjl.tools at gmail dot com 2015-02-04 19:35 ` hjl at gcc dot gnu.org 2015-02-04 19:37 ` hjl.tools at gmail dot com 2015-02-04 19:44 ` dominiq at lps dot ens.fr 2015-02-04 20:03 ` hjl.tools at gmail dot com 2015-02-05 10:04 ` dominiq at lps dot ens.fr 2015-02-05 10:08 ` ubizjak at gmail dot com 2015-02-05 10:37 ` uros at gcc dot gnu.org 2015-04-22 12:02 ` jakub at gcc dot gnu.org 2015-04-22 13:53 ` r.ayrapetyan at samsung dot com
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-64905-4-aSPmCHvmuZ@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).