public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55634] ARM: gcc vector extensions: storing vector to unaligned memory location does not use VST1.8 NEON instruction
Date: Mon, 05 Aug 2013 20:35:00 -0000	[thread overview]
Message-ID: <bug-55634-4-47noGzlw5w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55634-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55634

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-08-05
                 CC|                            |ramana at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
On AArch64 with no strict alignment we end up generating with .002t.original

trunk 


{
  T tmp = *a + *b;
  extern void * memcpy (void *, const void *, long unsigned int);

    T tmp = *a + *b;
  MEM[(char * {ref-all})result] = MEM[(char * {ref-all})&tmp];, result;
}



On A32 or indeed AArch64 with -mstrict-align we end up generating 

{
  T tmp = *a + *b;
  extern void * memcpy (void *, const void *, long unsigned int);

    T tmp = *a + *b;
  memcpy (result, (const void *) &tmp, 16);
}


Where do you expect the memcpy to have been made redundant or a use of the
appropriate movmisalign insn - richi ? 

Ramana


  parent reply	other threads:[~2013-08-05 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 22:16 [Bug target/55634] New: " siarhei.siamashka at gmail dot com
2012-12-10  9:41 ` [Bug target/55634] " rguenth at gcc dot gnu.org
2013-08-05 20:35 ` ramana at gcc dot gnu.org [this message]
2024-04-03  4:03 ` 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-55634-4-47noGzlw5w@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: link
Be 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).