public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, pb@nexus.co.uk, rearnsha@gcc.gnu.org Subject: Re: optimization/7056: [ARM] zero extend code worse in 3.1 than 3.0 Date: Mon, 29 Jul 2002 09:36:00 -0000 [thread overview] Message-ID: <20020729163610.743.qmail@sources.redhat.com> (raw) Synopsis: [ARM] zero extend code worse in 3.1 than 3.0 Responsible-Changed-From-To: unassigned->rearnsha Responsible-Changed-By: rearnsha Responsible-Changed-When: Mon Jul 29 09:36:09 2002 Responsible-Changed-Why: . State-Changed-From-To: analyzed->closed State-Changed-By: rearnsha State-Changed-When: Mon Jul 29 09:36:09 2002 State-Changed-Why: A useful side-effect of this change: 2002-07-22 Richard Earnshaw <rearnsha@arm.com> * arm.md (movqi): If optimizing and we can create pseudos, use a ZERO_EXTEND to load from memory, then copy the result into the target. (movhi): Likewise, but only for ARMv4. is that this problem no-longer occurs. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7056
next reply other threads:[~2002-07-29 16:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-29 9:36 rearnsha [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-17 9:56 rearnsha
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=20020729163610.743.qmail@sources.redhat.com \ --to=rearnsha@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=pb@nexus.co.uk \ /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).