public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/21501] ICE in extract_insn, at recog.c:2082
Date: Wed, 11 May 2005 09:36:00 -0000	[thread overview]
Message-ID: <20050511093645.19724.qmail@sourceware.org> (raw)
In-Reply-To: <20050510183334.21501.belyshev@depni.sinp.msu.ru>


------- Additional Comments From rearnsha at gcc dot gnu dot org  2005-05-11 09:36 -------
This compiles without problems for me with today's compiler:

$ /work/rearnsha/gnu/egcs/gcc/cc1 -O1 diff.c
 foo

Execution times (seconds)
 symout                :   0.00 ( 0%) usr   0.01 (100%) sys   0.01 (50%) wall
 TOTAL                 :   0.01             0.01             0.02
$ cat diff.s
        .file   "diff.c"
        .text
        .align  2
        .global foo
        .type   foo, %function
foo:
        @ args = 0, pretend = 0, frame = 0
        @ frame_needed = 0, uses_anonymous_args = 0
        @ link register save eliminated.
        @ lr needed for prologue
        mov     r3, #-67108864
        sub     r3, r3, #128
        add     r0, r0, r3
        bx      lr
        .size   foo, .-foo
        .ident  "GCC: (GNU) 4.1.0 20050511 (experimental)"

While developing the other patch that I committed at about the same time

2005-05-09  Richard Earnshaw  <richard.earnshaw@arm.com>

        * arm.c (const_ok_for_arm): Use a faster algorithm.

I did find that one of my machines (a netbsd-2.99 based machine with libraries
compiled for an ARMv5 core) had a buggy implementation of ffs(3).  If your
ffs(3) does not correctly determine the bottom bit in a constant, then the code
in const_ok_for_arm may well fail in the manner you describe.  That would be a
host bug, though.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WORKSFORME


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


  parent reply	other threads:[~2005-05-11  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 18:33 [Bug target/21501] New: " belyshev at depni dot sinp dot msu dot ru
2005-05-10 18:38 ` [Bug target/21501] " pinskia at gcc dot gnu dot org
2005-05-10 18:38 ` pinskia at gcc dot gnu dot org
2005-05-11  9:36 ` rearnsha at gcc dot gnu dot org [this message]
2005-05-11 22:41 ` belyshev at depni dot sinp dot msu dot ru
2005-05-11 23:13 ` [Bug target/21501] [4.1 regression] " belyshev at depni dot sinp dot msu dot ru
2005-05-12 10:37 ` cvs-commit at gcc dot gnu dot org
2005-05-12 10:41 ` rearnsha at gcc dot gnu dot org
2005-06-05  7:47 ` pinskia at gcc dot gnu dot 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=20050511093645.19724.qmail@sourceware.org \
    --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).