[Bug target/45814] ICE in extract_insn, at recog.c:2127

[rmansfield at qnx dot com]

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

Ryan Mansfield  changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Ryan Mansfield  ---
ARM OABI is no longer a supported target.

[Bug target/45814] ICE in extract_insn, at recog.c:2127

[rmansfield at qnx dot com]

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

--- Comment #2 from Ryan Mansfield  2011-01-08 
21:23:40 UTC ---
Nope, still broken on trunk for me.

$ ./xgcc -v
Using built-in specs.
COLLECT_GCC=./xgcc
Target: arm-unknown-linux-gnu
Configured with: ../configure --target=arm-unknown-linux-gnu
--prefix=//home/ryan/crosstool/4.2-20080312-glibc-2.3.6/arm-unknown-linux-gnu
--with-headers=//home/ryan/crosstool/4.2-20080312-glibc-2.3.6/arm-unknown-linux-gnu/arm-unknown-linux-gnu/include
--with-local-prefix=//home/ryan/crosstool/4.2-20080312-glibc-2.3.6/arm-unknown-linux-gnu/arm-unknown-linux-gnu
--disable-nls --enable-threads=posix --enable-symvers=gnu --enable-__cxa_atexit
--enable-languages=c++ --enable-shared --enable-c99 --enable-long-long
Thread model: posix
gcc version 4.6.0 20110108 (experimental) [trunk revision 168603] (GCC) 
$ ./xgcc -B. -march=armv6 -mfpu=vfp -mfloat-abi=softfp -O3 t.i -mapcs-frame -c
t.i: In function 'SendTg':
t.i:25:7: warning: incompatible implicit declaration of built-in function
'memset' [enabled by default]
t.i:39:1: error: unrecognizable insn:
(insn 155 154 156 6 (set (reg:HI 4 r4)
(reg:SI 77 s14)) t.i:30 -1
 (nil))
t.i:39:1: internal compiler error: in extract_insn, at recog.c:2109
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.

[Bug target/45814] ICE in extract_insn, at recog.c:2127

[ibolton at gcc dot gnu.org]

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

Ian Bolton  changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING
   Last reconfirmed||2011.01.07 11:44:57
 CC||ibolton at gcc dot gnu.org
 Ever Confirmed|0   |1

--- Comment #1 from Ian Bolton  2011-01-07 11:44:57 
UTC ---
I was able to replicate this with r165124 of trunk, but latest trunk is not
showing this problem.  Please can you confirm it is now working for you, Ryan.