Bug#336022: this is actually binutils bug

[Thiemo Seufer <ths@networkno.de>]

Sheplyakov Alexei wrote:
> Hello!
> 
> On Thu, 27 Oct 2005 15:12:54 +0200, Stefan Schmidt <zaphodb@zaphods.net> wrote:
> 
> > make bzImage CC=gcc-2.95
> > ..
> > make CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.31/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-alias
> > make[1]: Entering directory `/usr/src/linux-2.4.31/arch/i386/kernel'
> > gcc-2.95 -D__KERNEL__ -I/usr/src/linux-2.4.31/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
> > {standard input}: Assembler messages:
> > {standard input}:853: Error: suffix or operands invalid for `mov'
> > {standard input}:854: Error: suffix or operands invalid for `mov'
> > {standard input}:947: Error: suffix or operands invalid for `mov'
> > {standard input}:948: Error: suffix or operands invalid for `mov'
> > {standard input}:1006: Error: suffix or operands invalid for `mov'
> > {standard input}:1007: Error: suffix or operands invalid for `mov'
> > {standard input}:1009: Error: suffix or operands invalid for `mov'
> > {standard input}:1021: Error: suffix or operands invalid for `mov'
> > make[1]: *** [process.o] Error 1
> > make[1]: Leaving directory `/usr/src/linux-2.4.31/arch/i386/kernel'
> > make: *** [_dir_arch/i386/kernel] Error 2
> 
> I've seen such an error too. I don't think this is gcc-2.95 bug, since
> gcc-3.3 and gcc-3.4 fail with the same error message.
> This is binutils (version 2.16.1cvs20050902-1 and newer) bug (feature?).
> With binutils from testing (version 2.16.1-2) it is possible to compile
> the kernel with any gcc version (2.95, 3.3, 3.4).

Binutils tightened on ix86 the checks for potentially invalid operands
recently, thus, without having looked at the code, I'm inclined to claim
this is a problem in kernel 2.4.31.


Thiemo