This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/53266] Error: Unrecognized opcode: `mulhwu'
- From: "skunk at iskunk dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 27 Sep 2012 14:02:03 +0000
- Subject: [Bug bootstrap/53266] Error: Unrecognized opcode: `mulhwu'
- Auto-submitted: auto-generated
- References: <bug-53266-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53266
--- Comment #10 from Daniel Richard G. <skunk at iskunk dot org> 2012-09-27 14:02:03 UTC ---
Okay, I grabbed a copy of gcc-4.8-20120923, and started bootstrapping using an
older 4.5.2 (since the 4.7.0 C++ compiler isn't working correctly; am I correct
in observing that GCC can no longer be bootstrapped using just a C compiler?).
Things went well up until this point:
tg-g++ -c -g -DIN_GCC -fno-exceptions -fno-rtti -W -Wall -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -I.
-I. -I/home/src/gcc-4.8-20120923/gcc -I/home/src/gcc-4.8-20120923/gcc/.
-I/home/src/gcc-4.8-20120923/gcc/../include
-I/home/src/gcc-4.8-20120923/gcc/../libcpp/include
-I/tg/freeport/arch/aix32/include -I/tg/freeport/arch/aix32/include
-I/tg/freeport/arch/aix32/include
-I/home/src/gcc-4.8-20120923/gcc/../libdecnumber
-I/home/src/gcc-4.8-20120923/gcc/../libdecnumber/dpd -I../libdecnumber \
/home/src/gcc-4.8-20120923/gcc/config/rs6000/rs6000.c -o rs6000.o
/home/src/gcc-4.8-20120923/gcc/config/rs6000/rs6000.c: In function 'void
rs6000_code_end()':
/home/src/gcc-4.8-20120923/gcc/config/rs6000/rs6000.c:28292:51: error:
'ASM_WEAKEN_DECL' was not declared in this scope
gmake[3]: *** [rs6000.o] Error 1
gmake[3]: Leaving directory `/tmp/gcc-4.8-test/gcc'
gmake[2]: *** [all-stage1-gcc] Error 2
gmake[2]: Leaving directory `/tmp/gcc-4.8-test'
gmake[1]: *** [stage1-bubble] Error 2
gmake[1]: Leaving directory `/tmp/gcc-4.8-test'
gmake: *** [bootstrap-lean] Error 2
This is one of the issues addressed by my aforementioned patch.