public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "edmar at freescale dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30259]  New: [4.1 branch] ICE on valid code
Date: Tue, 19 Dec 2006 17:48:00 -0000	[thread overview]
Message-ID: <bug-30259-12262@http.gcc.gnu.org/bugzilla/> (raw)

Starting on December 17, the 4.1 branch fails to build for target e500v2.
The comfiguration is:
--target=powerpc-unknown-linux-gnuspe --enable-e500_double

The failure is:
/temp/gnu_toolchain/build_area/gcc-4_1-branch/obj_gcc-4_1-branch_e500v2/./gcc/xgcc
-B/temp/gnu_toolchain/build_area/gcc-4_1-branch/obj_gcc-4_1-
branch_e500v2/./gcc/
-B/temp/gnu_toolchain/install_area/gcc-4_1-branch/gcc-4_1-branch-20061218-e500v2/powerpc-unknown-linux-gnuspe/bin/
-B/temp
/gnu_toolchain/install_area/gcc-4_1-branch/gcc-4_1-branch-20061218-e500v2/powerpc-unknown-linux-gnuspe/lib/
-isystem /temp/gnu_toolchain/instal
l_area/gcc-4_1-branch/gcc-4_1-branch-20061218-e500v2/powerpc-unknown-linux-gnuspe/include
-isystem
/temp/gnu_toolchain/install_area/gcc-4_1-branch/gcc-4_1-branch-20061218-e500v2/powerpc-unknown-linux-gnuspe/sys-include
-O2  -O2 -g -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-string
s -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem
./include  -fPIC -specs=ldblspecs -g -DHAVE_GTHR_DEFAULT -DIN_LIBGC
C2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I -I../../gcc-4_1-branch/gcc
-I../../gcc-4_1-branch/gcc/ -I../../gcc-4_1-branch/gcc/../include
-I../../gcc-4_1-branch/gcc/../libcpp/include
-I/proj/ppc/sysperf/sw/gnu_toolchain/gcc_support/linuxAMD64/include
-I/proj/ppc/sysperf/sw/gnu_toolchain/gcc_support/linuxAMD64/include -DL_multc3
-c ../../gcc-4_1-branch/gcc/libgcc2.c -o libgcc/./_multc3.o
../../gcc-4_1-branch/gcc/libgcc2.c: In function '__multc3':
../../gcc-4_1-branch/gcc/libgcc2.c:1702: error: unrecognizable insn:
(insn 1229 1228 15 0 ../../gcc-4_1-branch/gcc/libgcc2.c:1643 (set (reg:DF 23 23
[orig:145 d+8 ] [145])
        (mem/c/i:DF (plus:SI (reg/f:SI 1 1)
                (const_int 256 [0x100])) [3 d+8 S8 A32])) -1 (nil)
    (nil))
../../gcc-4_1-branch/gcc/libgcc2.c:1702: internal compiler error: in
extract_insn, at recog.c:2084
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
gmake[3]: *** [libgcc/./_multc3.o] Error 1
gmake[3]: Leaving directory
`/temp/gnu_toolchain/build_area/gcc-4_1-branch/obj_gcc-4_1-branch_e500v2/gcc'
gmake[2]: *** [stmp-multilib] Error 2
gmake[2]: Leaving directory
`/temp/gnu_toolchain/build_area/gcc-4_1-branch/obj_gcc-4_1-branch_e500v2/gcc'
gmake[1]: *** [all-gcc] Error 2
gmake[1]: Leaving directory
`/temp/gnu_toolchain/build_area/gcc-4_1-branch/obj_gcc-4_1-branch_e500v2'
gmake: *** [all] Error 2


-- 
           Summary: [4.1 branch] ICE on valid code
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: edmar at freescale dot com
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: powerpc-unknown-linux-gnuspe


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


             reply	other threads:[~2006-12-19 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 17:48 edmar at freescale dot com [this message]
2006-12-19 18:16 ` [Bug c/30259] " joseph at codesourcery dot com
2006-12-19 18:50 ` edmar at freescale dot com
2006-12-19 21:34 ` joseph at codesourcery dot com
2006-12-20 16:11 ` [Bug target/30259] " edmar at freescale dot com
2007-02-04 16:40 ` [Bug target/30259] " guenter at roeck-us dot net

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-30259-12262@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).