[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#432489: gcc-4.2: error when compiling kernel 2.6.22: Error: too many memory references for `lea'



Package: gcc-4.2
Version: 4.2-20070707-1
Severity: normal

I unable to compile released kernel 2.6.22 with gcc-4.2:
gcc-4.2 (GCC) 4.2.1 20070707 (prerelease) (Debian 4.2-20070707-1)

The compilation ends up with the following error:

  CC      fs/binfmt_misc.o                                                                                                  
  {standard input}: Assembler messages:                                                                                     
  {standard input}:697: Error: too many memory references for `lea'                                                         
  make[1]: *** [fs/binfmt_misc.o] Error 1                                                                                   
  make: *** [fs] Error 2         

The very same kernel sources with the very same configuration are compiled with gcc-4.1 without any errors.
So, it must be some kind of regression.

Regards,
Max


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.21.1
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.2 depends on:
ii  binutils               2.17cvs20070426-8 The GNU assembler, linker and bina
ii  cpp-4.2                4.2-20070707-1    The GNU C preprocessor
ii  gcc-4.2-base           4.2-20070707-1    The GNU Compiler Collection (base 
ii  libc6                  2.5-11            GNU C Library: Shared libraries
ii  libgcc1                1:4.2-20070707-1  GCC support library
ii  libgomp1               4.2-20070707-1    GCC OpenMP (GOMP) support library

Versions of packages gcc-4.2 recommends:
ii  libc6-dev                     2.5-11     GNU C Library: Development Librari
pn  libmudflap0-4.2-dev           <none>     (no description available)

-- debconf-show failed



Reply to: