From: Bernardo Innocenti <bernie@develer.com>
To: gcc@gcc.gnu.org
Cc: Richard Zidlicky <rz@linux-m68k.org>,
Andreas Schwab <schwab@suse.de>, Gunther Nikl <gni@gecko.de>
Subject: more m68k breakage on m68k-linux
Date: Sun, 18 Jan 2004 01:50:00 -0000 [thread overview]
Message-ID: <4009E670.5090600@develer.com> (raw)
Hello,
I'm now testing on m68k-linux as well as m68k-netbsdelf and m68k-uclinux.
I see a new ICE during bootstrap, even with Andreas patch installed.
It happens *only* on m68k-linux, but the checkous have been done a few
days from each other.
./xgcc -B./ -B/warez/gcc/m68k-linux-HEAD-install/m68k-unknown-linux-gnu/bin/ -isystem /warez/gcc/m68k-linux-HEAD-install/m68k-unknown-linux-gnu/include -isystem /warez/gcc/m68k-linux-HEAD-install/m68k-unknown-linux-gnu/sys-include -L/home/bernie/src/m68k-linux-HEAD-build/gcc/../ld -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../combined-HEAD/gcc -I../../combined-HEAD/gcc/. -I../../combined-HEAD/gcc/../include -DL_cmpdi2 -c ../../combined-HEAD/gcc/libgcc2.c -o libgcc/./_cmpdi2.o
../../combined-HEAD/gcc/libgcc2.c: In function `__cmpdi2':
../../combined-HEAD/gcc/libgcc2.c:1081: error: unrecognizable insn:
(insn 34 27 28 2 ../../combined-HEAD/gcc/libgcc2.c:1075 (set (strict_low_part (reg:QI 2 %d2))
(const_int 2 [0x2])) -1 (nil)
(expr_list:REG_EQUAL (const_int 2 [0x2])
(nil)))
../../combined-HEAD/gcc/libgcc2.c:1081: internal compiler error: in extract_insn, at recog.c:2083
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next reply other threads:[~2004-01-18 1:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 1:50 Bernardo Innocenti [this message]
2004-01-18 4:52 ` Bernardo Innocenti
2004-01-18 9:59 ` Matthias Klose
2004-01-18 10:07 ` Bernardo Innocenti
2004-01-20 9:15 ` Andreas Schwab
2004-01-20 10:36 ` Bernardo Innocenti
2004-03-01 20:15 ` Richard Zidlicky
2004-03-01 22:05 ` Richard Zidlicky
2004-03-02 0:18 ` Bernardo Innocenti
2004-03-02 9:14 ` Richard Zidlicky
2004-03-02 10:42 ` Gunther Nikl
2004-03-02 18:19 ` Richard Henderson
2004-03-02 19:33 ` Roman Zippel
2004-03-02 21:32 ` Richard Henderson
2004-03-02 22:26 ` Richard Zidlicky
2004-03-03 8:53 ` Bernardo Innocenti
2004-03-03 10:13 ` Roman Zippel
2004-03-03 11:03 ` Andreas Schwab
2004-03-03 22:38 ` Bernardo Innocenti
2004-03-04 0:35 ` Richard Henderson
2004-03-04 7:25 ` Gunther Nikl
2004-03-04 18:45 ` Richard Zidlicky
2004-03-04 22:46 ` Andreas Schwab
2004-03-04 10:58 ` Gunther Nikl
2004-03-04 13:27 ` Bernardo Innocenti
2004-03-04 13:45 ` Roman Zippel
2004-03-04 15:32 ` Gunther Nikl
2004-03-07 15:05 ` Bernardo Innocenti
2004-03-08 16:31 ` Gunther Nikl
2004-03-08 21:38 ` Bernardo Innocenti
2004-03-09 8:40 ` Gunther Nikl
2004-03-09 22:35 ` Bernardo Innocenti
[not found] ` <20040308181401.0DB3498C8A@baradas.org>
2004-03-08 21:45 ` You ucLinux patches break RTEMS building Bernardo Innocenti
2004-03-03 8:22 ` more m68k breakage on m68k-linux Bernardo Innocenti
2004-03-03 13:27 ` Richard Zidlicky
2004-03-01 22:30 ` Andreas Schwab
2004-03-02 0:07 ` Bernardo Innocenti
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=4009E670.5090600@develer.com \
--to=bernie@develer.com \
--cc=gcc@gcc.gnu.org \
--cc=gni@gecko.de \
--cc=rz@linux-m68k.org \
--cc=schwab@suse.de \
/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).