[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#380374: marked as done (FTBFS on m68k: ICE in extract_insn, at recog.c:2077)

Your message dated Wed, 13 Sep 2006 12:54:16 +0200
with message-id <20060913105416.GA31444@deprecation.cyrius.com>
and subject line not reproducible
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gcc-snapshot
Version: 20060721-1
Severity: important

/build/buildd/gcc-snapshot-20060721/build/./prev-gcc/xgcc -B/build/buildd/gcc-snapshot-20060721/build/./prev-gcc/ -B/usr/lib/gcc-snapshot/m68k-linux-gnu/bin/ -c   -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -fno-common   -DHAVE_CONFIG_H -I. -I. -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/../include -I../../src/gcc/../libcpp/include  -I../../src/gcc/../libdecnumber -I../libdecnumber    ../../src/gcc/tree-data-ref.c -o tree-data-ref.o
../../src/gcc/tree-data-ref.c: In function 'object_analysis':
../../src/gcc/tree-data-ref.c:1815: error: unrecognizable insn:
(insn 2131 2130 2132 272 (set (cc0)
        (compare (reg:QI 127 [ D.27449 ])
            (const_int 32 [0x20]))) -1 (nil)
../../src/gcc/tree-data-ref.c:1815: internal compiler error: in extract_insn, at recog.c:2077
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

Martin Michlmayr

--- End Message ---
--- Begin Message ---
I think this might have been a hardware problem.  Neither I nor the
m68k people can reproduce this failure.
Martin Michlmayr

--- End Message ---

Reply to: