public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eric.batut at allegorithmic dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51968] gcc trunk (ARM) ICEs in final_scan_insn in final.c:2716, with "could not split insn" error msg
Date: Tue, 24 Jan 2012 11:56:00 -0000	[thread overview]
Message-ID: <bug-51968-4-nzqrzhQEE8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51968-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Eric Batut <eric.batut at allegorithmic dot com> 2012-01-24 11:12:23 UTC ---
(In reply to comment #3)
> Created attachment 26436 [details]
> proposed patch
> 
> I'll run this through a cross-build first, but I expect this will fix it.

This patch makes gcc trunk no longer crash with our Neon files. Building right
now to test for code correctness, although judging from the patch the
functionality of the code should not be impacted.

Thanks Richard !


  parent reply	other threads:[~2012-01-24 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 17:01 [Bug target/51968] New: " eric.batut at allegorithmic dot com
2012-01-23 17:57 ` [Bug target/51968] " eric.batut at allegorithmic dot com
2012-01-23 18:35 ` rth at gcc dot gnu.org
2012-01-23 18:40 ` rth at gcc dot gnu.org
2012-01-23 22:23 ` jakub at gcc dot gnu.org
2012-01-24 11:56 ` eric.batut at allegorithmic dot com [this message]
2012-01-24 11:59 ` eric.batut at allegorithmic dot com
2012-01-24 19:03 ` rth at gcc dot gnu.org
2012-01-24 19:07 ` rth at gcc dot gnu.org
2012-01-25 10:06 ` eric.batut at allegorithmic dot com

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-51968-4-nzqrzhQEE8@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).