gcc-4.4 ICE
Hi *,
any idea, before I “dig” deeper (if I can, what I don’t believe)?
gcc-4.4 (4.4.5-3+m68k.1) unreleased; urgency=low
* debian/patches/gcc-multiarch.diff: Add m68k support.
* debian/rules2: Disable multi{arch,lib} on m68k for now.
* debian/patches/pr41302.diff: new.
* debian/rules.patch: Add pr41302 on m68k.
-- Thorsten Glaser <tg@mirbsd.de> Sat, 16 Oct 2010 16:09:39 +0000
This is based directly on 4.4.5-3 from unstable.
/bin/sh ../../libtool --tag CXX --mode=compile /root/gcc-4.4-4.4.5/build/./gcc/xgcc -shared-libgcc -B/root/gcc-4.4-4.4.5/build/./gcc -nostdinc++ -L/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/src -L/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/src/.libs -B/usr/m68k-linux-gnu/bin/ -B/usr/m68k-linux-gnu/lib/ -isystem /usr/m68k-linux-gnu/include -isystem /usr/m68k-linux-gnu/sys-include -I/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/include/m68k-linux-gnu -I/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/include -I/root/gcc-4.4-4.4.5/src/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g3 -O0 -std=gnu++0x -c ../../../../../src/libstdc++-v3/src/mutex.cc
libtool: compile: /root/gcc-4.4-4.4.5/build/./gcc/xgcc -shared-libgcc -B/root/gcc-4.4-4.4.5/build/./gcc -nostdinc++ -L/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/src -L/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/src/.libs -B/usr/m68k-linux-gnu/bin/ -B/usr/m68k-linux-gnu/lib/ -isystem /usr/m68k-linux-gnu/include -isystem /usr/m68k-linux-gnu/sys-include -I/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/include/m68k-linux-gnu -I/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/include -I/root/gcc-4.4-4.4.5/src/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g3 -O0 -std=gnu++0x -c ../../../../../src/libstdc++-v3/src/mutex.cc -fPIC -DPIC -o .libs/mutex.o
../../../../../src/libstdc++-v3/src/mutex.cc: In function 'void std::__once_proxy()':
../../../../../src/libstdc++-v3/src/mutex.cc:97: error: insn does not satisfy its constraints:
(insn 26 34 5 ../../../../../src/libstdc++-v3/src/mutex.cc:96 (set (reg:SI 0 %d0 [31])
(const:SI (unspec:SI [
(symbol_ref:SI ("_ZSt11__once_call") [flags 0x10] <var_decl 0xc0fa9cb8 __once_call>)
(const_int 1 [0x1])
] 6))) 35 {*movsi_m68k} (nil))
../../../../../src/libstdc++-v3/src/mutex.cc:97: internal compiler error: in final_scan_insn, at final.c:2537
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make[7]: *** [mutex.lo] Error 1
make[7]: Leaving directory `/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/src/debug'
make[6]: *** [build_debug] Error 2
make[6]: Leaving directory `/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3/src'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/root/gcc-4.4-4.4.5/build/m68k-linux-gnu/libstdc++-v3'
make[3]: *** [all-target-libstdc++-v3] Error 2
make[3]: Leaving directory `/root/gcc-4.4-4.4.5/build'
make[2]: *** [bootstrap-lean] Error 2
make[2]: Leaving directory `/root/gcc-4.4-4.4.5/build'
s=`cat status`; rm -f status; test $s -eq 0
make[1]: *** [stamps/05-build-stamp] Error 1
make[1]: Leaving directory `/root/gcc-4.4-4.4.5'
make: *** [stamps/05-build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
81 extern "C"
82 {
83 void __once_proxy()
84 {
85 #ifndef _GLIBCXX_HAVE_TLS
86 function<void()> __once_call = std::move(__once_functor);
87 if (unique_lock<mutex>* __lock = __get_once_functor_lock_ptr())
88 {
89 // caller is using new ABI and provided lock ptr
90 __get_once_functor_lock_ptr() = 0;
91 __lock->unlock();
92 }
93 else
94 __get_once_functor_lock().unlock(); // global lock
95 #endif
96 __once_call();
97 }
98 }
bye,
//mirabilos
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence. -- Coywolf Qi Hunt
Reply to: