linux-kernel - build failure of malta_qemu_32r6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <YG35ULOblq/gUZmh@debian>
Date:   Wed, 7 Apr 2021 19:26:24 +0100
From:   Sudip Mukherjee <sudipm.mukherjee@...il.com>
To:     Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: build failure of malta_qemu_32r6_defconfig

Hi Thomas,

I was building v5.10.28 with malta_qemu_32r6_defconfig and noticed that
it fails to build, so tried next-20210407 to see if it has been fixed.
But linux-next also has the issue with gcc-10.

The error is:

./arch/mips/include/asm/vdso/gettimeofday.h: In function '__vdso_clock_gettime':
./arch/mips/include/asm/vdso/gettimeofday.h:103:2: error: the register 'lo' cannot be clobbered in 'asm' for the current target
  103 |  asm volatile(
      |  ^~~
./arch/mips/include/asm/vdso/gettimeofday.h: In function '__vdso_gettimeofday':
./arch/mips/include/asm/vdso/gettimeofday.h:33:2: error: the register 'lo' cannot be clobbered in 'asm' for the current target
   33 |  asm volatile(
      |  ^~~
./arch/mips/include/asm/vdso/gettimeofday.h: In function '__vdso_clock_getres':
./arch/mips/include/asm/vdso/gettimeofday.h:123:2: error: the register 'lo' cannot be clobbered in 'asm' for the current target
  123 |  asm volatile(
      |  ^~~
./arch/mips/include/asm/vdso/gettimeofday.h: In function '__vdso_clock_gettime64':
./arch/mips/include/asm/vdso/gettimeofday.h:57:2: error: the register 'lo' cannot be clobbered in 'asm' for the current target
   57 |  asm volatile(
      |  ^~~

Any idea how to fix this? Please ignore if it has been reported before.


--
Regards
Sudip