public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63277] ARM - NEON excessive use of vmov for vtbl2 / uint8x8x2 for shuffling data unnecessarily around Date: Tue, 16 Sep 2014 13:20:00 -0000 [thread overview] Message-ID: <bug-63277-4-ujUehnsLRE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63277-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63277 ktkachov at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Target| |arm Status|UNCONFIRMED |NEW Last reconfirmed| |2014-09-16 CC| |ktkachov at gcc dot gnu.org Ever confirmed|0 |1 Known to fail| |5.0 --- Comment #1 from ktkachov at gcc dot gnu.org --- Confirmed. The vmovs and vswp are generated from the implementation of our vcombine. The define_insn_and split for neon_vcombine<mode> splits into moves/swaps after reload, thus not giving the register allocator a chance to optimise the moves away.
next prev parent reply other threads:[~2014-09-16 13:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-16 12:07 [Bug target/63277] New: " janne-gcc at jannau dot net 2014-09-16 13:20 ` ktkachov at gcc dot gnu.org [this message] 2014-09-16 14:45 ` [Bug target/63277] " janne-gcc at jannau dot net 2014-09-16 14:45 ` janne-gcc at jannau dot net 2014-09-18 1:26 ` cbaylis at gcc dot gnu.org 2015-05-14 10:31 ` [Bug rtl-optimization/63277] " ramana at gcc dot gnu.org 2015-06-25 20:51 ` ramana 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-63277-4-ujUehnsLRE@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).