public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Michael dot Link at adc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/15499] New: ICE in copyprop_hardreg_forward_1 on cross compile for ARM
Date: Tue, 18 May 2004 10:39:00 -0000 [thread overview]
Message-ID: <20040517191254.15499.Michael.Link@adc.com> (raw)
Internal compiler error when compiling OpenSSL 0.9.7d. I didn't encounter this
error when using -Os.
$ arm-9tdmi-linux-gnu-gcc -I.. -I../.. -I../../include -fPIC -DZLIB_SHARED
-DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-DOPENSSL_NO_KRB5 -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall
--save-temps -c -o pem_info.o pem_info.c
pem_info.c: In function `PEM_X509_INFO_read_bio':
pem_info.c:275: error: insn does not satisfy its constraints:
(insn:HI 828 1799 832 23 (set (mem/s:SI (post_modify:SI (reg:SI 1 r1 [orig:343
<variable>.dec_pkey ] [343])
(plus:SI (reg:SI 1 r1 [orig:343 <variable>.dec_pkey ] [343])
(const_int 12 [0xc]))) [5 <variable>.type+0 S4 A32])
(reg:SI 8 r8 [344])) 125 {*arm_movsi_insn} (insn_list 827 (insn_list 826
(nil)))
(expr_list:REG_DEAD (reg:SI 8 r8 [344])
(expr_list:REG_INC (reg:SI 1 r1 [orig:343 <variable>.dec_pkey ] [343])
(expr_list:REG_EQUAL (const_int 6 [0x6])
(nil)))))
pem_info.c:275: internal compiler error: in copyprop_hardreg_forward_1, at
regrename.c:1549
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
$ arm-9tdmi-linux-gnu-gcc -v
Reading specs from
/opt/crosstool/arm-9tdmi-linux-gnu/gcc-3.4.0-glibc-2.3.2/lib/gcc/arm-9tdmi-linux-gnu/3.4.0/specs
Configured with:
/home/linkm/crosstool-0.28-rc13/build/arm-9tdmi-linux-gnu/gcc-3.4.0-glibc-2.3.2/gcc-3.4.0/configure
--target=arm-9tdmi-linux-gnu --host=i686-host_pc-linux-gnu
--prefix=/opt/crosstool/arm-9tdmi-linux-gnu/gcc-3.4.0-glibc-2.3.2
--with-cpu=arm9tdmi --enable-cxx-flags=-mcpu=arm9tdmi
--with-headers=/opt/crosstool/arm-9tdmi-linux-gnu/gcc-3.4.0-glibc-2.3.2/arm-9tdmi-linux-gnu/include
--with-local-prefix=/opt/crosstool/arm-9tdmi-linux-gnu/gcc-3.4.0-glibc-2.3.2/arm-9tdmi-linux-gnu
--disable-nls --enable-threads=posix --enable-symvers=gnu --enable-__cxa_atexit
--enable-languages=c,c++ --enable-shared --enable-c99 --enable-long-long
Thread model: posix
gcc version 3.4.0
--
Summary: ICE in copyprop_hardreg_forward_1 on cross compile for
ARM
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: Michael dot Link at adc dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-host_pc-linux-gnu
GCC host triplet: i686-host_pc-linux-gnu
GCC target triplet: arm-9tdmi-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15499
next reply other threads:[~2004-05-17 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:39 Michael dot Link at adc dot com [this message]
2004-05-18 10:51 ` [Bug c/15499] " Michael dot Link at adc dot com
2004-05-18 10:53 ` Michael dot Link at adc dot com
2004-05-18 11:04 ` [Bug target/15499] " pinskia at gcc dot gnu dot org
2004-05-18 11:16 ` pinskia at gcc dot gnu dot org
2004-06-22 6:56 ` mbritten at monochromatic dot net
2004-08-05 11:00 ` rearnsha at gcc dot gnu dot org
2004-08-25 17:03 ` 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=20040517191254.15499.Michael.Link@adc.com \
--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).