public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "corsepiu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35072]  New: h8300: ICE unwind-dw2-fde.c:650: error: unrecognizable insn
Date: Mon, 04 Feb 2008 06:44:00 -0000	[thread overview]
Message-ID: <bug-35072-9565@http.gcc.gnu.org/bugzilla/> (raw)

Building today's gcc-trunk (rev. 132088/2008-02-04) for target h8300-rtems4.9
fails with an ICE:
...
/users/rtems/src/toolchains/BUILD/h8300-rtems4.9/./gcc/xgcc
-B/users/rtems/src/toolchains/BUILD/h8300-rtems4.9/./gcc/ -nostdinc
-B/users/rtems/src/toolchains/BUILD/h8300-rtems4.9/h8300-rtems4.9/newlib/
-isystem
/users/rtems/src/toolchains/BUILD/h8300-rtems4.9/h8300-rtems4.9/newlib/targ-include
-isystem /users/rtems/src/toolchains/gcc-trunk/newlib/libc/include
-B/opt/rtems-4.9/h8300-rtems4.9/bin/ -B/opt/rtems-4.9/h8300-rtems4.9/lib/
-isystem /opt/rtems-4.9/h8300-rtems4.9/include -isystem
/opt/rtems-4.9/h8300-rtems4.9/sys-include -O2 -g -g -O2 -O2
-I../../../gcc-trunk/gcc/../newlib/libc/sys/rtems/include -O2 -g -g -O2  
-DIN_GCC -DCROSS_DIRECTORY_STRUCTURE   -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem
./include  -DDF=SF -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-Dinhibit_libc  -I. -I. -I../.././gcc -I../../../../gcc-trunk/libgcc
-I../../../../gcc-trunk/libgcc/. -I../../../../gcc-trunk/libgcc/../gcc
-I../../../../gcc-trunk/libgcc/../include  -DHAVE_CC_TLS -o unwind-dw2-fde.o
-MT unwind-dw2-fde.o -MD -MP -MF unwind-dw2-fde.dep -fexceptions -c
../../../../gcc-trunk/libgcc/../gcc/unwind-dw2-fde.c 
../../../../gcc-trunk/libgcc/../gcc/unwind-dw2-fde.c: In function
'classify_object_over_fdes':
../../../../gcc-trunk/libgcc/../gcc/unwind-dw2-fde.c:650: error: unrecognizable
insn:
(insn 84 83 85 12 ../../../../gcc-trunk/libgcc/../gcc/unwind-dw2-fde.c:625 (set
(zero_extract:HI (subreg:HI (reg:QI 55) 0)
            (const_int 1 [0x1])
            (const_int 5 [0x5]))
        (const_int 1 [0x1])) -1 (nil))
../../../../gcc-trunk/libgcc/../gcc/unwind-dw2-fde.c:650: internal compiler
error: in extract_insn, at recog.c:1990
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [unwind-dw2-fde.o] Error 1
make[2]: Leaving directory
`/users/rtems/src/toolchains/BUILD/h8300-rtems4.9/h8300-rtems4.9/libgcc'
make[1]: *** [all-target-libgcc] Error 2


-- 
           Summary: h8300: ICE unwind-dw2-fde.c:650: error: unrecognizable
                    insn
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: corsepiu at gcc dot gnu dot org
GCC target triplet: h8300-rtems*


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


             reply	other threads:[~2008-02-04  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04  6:44 corsepiu at gcc dot gnu dot org [this message]
2008-02-06  4:16 ` [Bug target/35072] " corsepiu at gcc dot gnu dot org
2008-02-19 19:13 ` joel at gcc dot gnu dot org
2010-02-24 20:29 ` law at redhat 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-35072-9565@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).