linux-kernel - Re: [kbuild-all] mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal'

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Apr 2016 20:55:34 +0100
From:	"Maciej W. Rozycki" <macro@...tec.com>
To:	Fengguang Wu <fengguang.wu@...el.com>
CC:	Ralf Baechle <ralf@...ux-mips.org>, <kbuild-all@...org>,
	Paul Burton <paul.burton@...tec.com>,
	<linux-kernel@...r.kernel.org>, Philip Li <philip.li@...el.com>
Subject: Re: [kbuild-all] mipsel-linux-gnu-gcc: error: unrecognized command
 line option '-mcompact-branches=optimal'

On Thu, 21 Apr 2016, Fengguang Wu wrote:

> > -mcompact-branches=optimal is an option for the latest version of the MIPS
> > architecture which is enabled by mips-malta_qemu_32r6_defconfig but your
> > compiler is too old, doesn't support R6.  Unfortunately there's no simple
> > way to run a test on the build environment from kconfig or even before
> > kconfig runs so we've just ignord this particular build issue.  Plus
> > there being the additional issue that we only know the toolchain to be
> > used after certain options have been picked.
> 
> We are running Debian's mips cross compiler.
> 
> % mips-linux-gnu-gcc --version
> mips-linux-gnu-gcc (Debian 5.2.1-16) 5.2.1 20150903
> Copyright (C) 2015 Free Software Foundation, Inc.
> 
> How about temporarily disable that error, until we upgrade to a new
> gcc version which supports the -mcompact-branches option?

 I don't think it makes sense as the compiler won't support MIPSr6 code 
anyway, so first it'll bail out on `-march=mips32r6', and if we go even 
further and disable that too, then GAS will probably break somewhere on 
inline asm and GCC will produce code which does not make sense otherwise.

  Maciej