linux-kernel - Re: [PATCH] kbuild: Fix gcc -x syntax

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:	Sat, 29 Sep 2012 10:34:00 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Jean Delvare <jdelvare@...e.de>, linux-kernel@...r.kernel.org,
	x86@...nel.org, Michal Marek <mmarek@...e.cz>,
	Ralf Baechle <ralf@...ux-mips.org>
Subject: Re: [PATCH] kbuild: Fix gcc -x syntax


* Bernhard Walle <bernhard@...lle.de> wrote:

> Hi,
> 
> * Ingo Molnar <mingo@...nel.org> [2012-09-29 08:37]:
> > * Jean Delvare <jdelvare@...e.de> wrote:
> > 
> > > The correct syntax for gcc -x is "gcc -x assembler", not "gcc 
> > > -xassembler". Even though the latter happens to work, the 
> > > former is what is documented in the manual page and thus what 
> > > gcc wrappers such as icecream do expect.
> > > 
> > > This isn't a cosmetic change. The missing space prevents 
> > > icecream from recognizing compilation tasks it can't handle, 
> > > leading to silent kernel miscompilations.
> > 
> > Although we can apply this patch, it won't solve the problem of 
> > building older kernels (and bisecting, etc.).
> > 
> > Wouldn't it be prudent to increase the compatibility of 
> > icecream, so that it accepts what GCC accepts in practice,
> > such as -xassembler?
> 
> Wouldn't it make sense to do both? Using the documented syntax 
> in the build system *and* increase compatibility in 3rd party 
> tools?

Yes.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/