public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thejes.k at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51819] [4.7 Regression] Neon wrong code generation, Error: unsupported alignment for instruction -- `vst1.32 {d2[0]},[r0:64]'
Date: Fri, 13 Jan 2012 05:33:00 -0000	[thread overview]
Message-ID: <bug-51819-4-61JZAijpOQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51819-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Thejes Kuttian <thejes.k at gmail dot com> 2012-01-13 05:32:48 UTC ---
(In reply to comment #1)
> Completely untested but I think this is the correct fix for this problem. 
> 
> 
> 
> 
> diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
> index 4c310d4..31f03cc 100644
> --- a/gcc/config/arm/arm.c
> +++ b/gcc/config/arm/arm.c
> @@ -17720,7 +17720,7 @@ arm_print_operand (FILE *stream, rtx x, int code)
>           align_bits = 256;
>         else if ((memsize == 8 || memsize == 16) && (align % 16) == 0)
>           align_bits = 128;
> -       else if ((align % 8) == 0)
> +       else if ((memsize >= 8) && (align % 8) == 0)
>           align_bits = 64;
>         else
>           align_bits = 0;

Confirmed. This patch fixes the issue for me .


  parent reply	other threads:[~2012-01-13  5:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11  5:44 [Bug target/51819] New: [4.7 Regression ]Neon " thejes.k at gmail dot com
2012-01-11  9:36 ` [Bug target/51819] [4.7 Regression] Neon " rguenth at gcc dot gnu.org
2012-01-11 14:52 ` ramana at gcc dot gnu.org
2012-01-13  5:33 ` thejes.k at gmail dot com [this message]
2012-01-19 12:57 ` rguenth at gcc dot gnu.org
2012-01-20 10:16 ` ramana at gcc dot gnu.org
2012-01-20 13:38 ` ramana at gcc dot gnu.org
2012-01-20 14:17 ` ramana at gcc dot gnu.org
2012-04-16 15:20 ` uweigand 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-51819-4-61JZAijpOQ@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).