public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/67305] [6 Regression] gcc.c-torture/compile/20121027-1.c ICE on arm-none-eabi
Date: Mon, 28 Sep 2015 21:23:00 -0000	[thread overview]
Message-ID: <bug-67305-4-qp8KfU0KP5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67305-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67305

Jim Wilson <wilson at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wilson at gcc dot gnu.org

--- Comment #8 from Jim Wilson <wilson at gcc dot gnu.org> ---
Yes, neon_vector_mem_operand is broken.  The first if statement should not be
returning !strict.  I'd add a "strict &&" test to the if statement, and then
return FALSE, to make it look more like the test in the immediately preceding
function, but Segher's suggestion would work also.  Without the quick exit, the
code will do the regular address checks, and the testcase will work fine, the
invalid address will be rejected.


      parent reply	other threads:[~2015-09-28 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  9:55 [Bug tree-optimization/67305] New: [6 Regression] gcc.c-torture/compile/20121027-1.c ICE jiwang at gcc dot gnu.org
2015-08-21 10:30 ` [Bug rtl-optimization/67305] " rguenth at gcc dot gnu.org
2015-08-26 17:29 ` vmakarov at gcc dot gnu.org
2015-08-28 15:05 ` jiwang at gcc dot gnu.org
2015-08-28 15:33 ` jiwang at gcc dot gnu.org
2015-08-28 16:56 ` segher at gcc dot gnu.org
2015-08-28 20:13 ` [Bug target/67305] " segher at gcc dot gnu.org
2015-09-28 21:23 ` wilson at gcc dot gnu.org [this message]

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-67305-4-qp8KfU0KP5@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).