public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45511] ICE in neon_valid_immediate, at config/arm/arm.c:8294
Date: Thu, 16 Jun 2011 23:01:00 -0000	[thread overview]
Message-ID: <bug-45511-4-b93YVBJuQM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45511-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Ryan Mansfield <rmansfield at qnx dot com> 2011-06-16 23:00:25 UTC ---
(In reply to comment #5)
> EABI targets force 64-bit HOST_WIDE_INT, so the vast majority of users of 
> the ARM port won't hit this assert.  If you really care about old-ABI 
> targets (and deprecation of arm-linux-gnu and arm-elf is long overdue), 
> maybe ARM should just force 64-bit HOST_WIDE_INT unconditionally.

Thanks for replying, JSM. Looking at config.gcc, there still seems to be a
quite a number of targets that still use the apcs-gnu ABI. Are you suggesting
all of the non-EABI targets be deprecated, or just the arm-linux-gnu/arm-elf
configurations? Is there any downside or reason why not to add
need_64bit_hwint=yes for all arm targets?


  parent reply	other threads:[~2011-06-16 23:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45511-4@http.gcc.gnu.org/bugzilla/>
2011-06-16 20:18 ` rmansfield at qnx dot com
2011-06-16 21:07 ` joseph at codesourcery dot com
2011-06-16 23:01 ` rmansfield at qnx dot com [this message]
2011-06-16 23:16 ` joseph at codesourcery dot com
2013-12-17 16:42 ` rmansfield at qnx dot com
2010-09-03  1:13 [Bug target/45511] New: " rmansfield at qnx dot com
2010-09-03  1:13 ` [Bug target/45511] " rmansfield at qnx dot com
2010-09-03 10:43 ` ramana at gcc dot gnu dot org
2010-09-03 13:02 ` rmansfield at qnx 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-45511-4-b93YVBJuQM@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).