On Fri, 12 Apr 2013, David Daney wrote: > I just tried to bootstrap on o32 Debian. This system has binutils 2.20.1. > > Here is a sample of the resulting failure when building the libjava target > libs: > . > . > . > /home/daney/gccsvn/build/./gcc/xgcc -B/home/daney/gccsvn/build/./gcc/ > -B/usr/local/mips-unknown-linux-gnu/bin/ > -B/usr/local/mips-unknown-linux-gnu/lib/ -isystem > /usr/local/mips-unknown-linux-gnu/include -isystem > /usr/local/mips-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H -I. > -I../../../../trunk/libjava/libltdl -g -O2 -minterlink-mips16 -c > ../../../../trunk/libjava/libltdl/ltdl.c -fPIC -DPIC -o .libs/ltdl.o > /tmp/cckECtVQ.s: Assembler messages: > /tmp/cckECtVQ.s:12: Warning: Tried to set unrecognized symbol: nomicromips > > /tmp/cckECtVQ.s:115: Warning: Tried to set unrecognized symbol: nomicromips > > /tmp/cckECtVQ.s:161: Warning: Tried to set unrecognized symbol: nomicromips > . > . > . > > There are literally thousands and thousands of these warnings.
Thanks for the report, I guess GCC should: 1. Detect in its `configure' script if GAS supports the pseudo-op and refrain from producing it if it does not (or actually perhaps it may never produce it by default as GAS defaults to the nomicromips mode anyway); we have precedents for that already. 2. Refuse the -mmicromips option and terminate if GAS does not support the micromips mode; we have precedents for that too. 3. If support for pure-microMIPS processors is added in the future, then refuse to select that processor (with -march=) or being configured for that processor by default (with a `configure' option) altogether unless GAS supports the micromips mode. Thoughts? Maciej
