linux-kernel - Re: [PATCH resend] Kbuild: x86: Eliminate duplicate command line options

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]

Message-ID: <CAOFdcFMwEbvRAheZ5RD20nU1GcaMJXy=o5=fsaiFudy+cyiZuQ@mail.gmail.com>
Date:	Wed, 10 Sep 2014 13:59:50 -0400
From:	Peter Foley <pefoley2@...oley.com>
To:	Rasmus Villemoes <linux@...musvillemoes.dk>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH resend] Kbuild: x86: Eliminate duplicate command line options

On Wed, Sep 10, 2014 at 12:05 PM, Rasmus Villemoes
<linux@...musvillemoes.dk> wrote:
> The options -mno-mmx and -mno-sse are unconditionally added to
> KBUILD_CFLAGS in both branches of an ifeq and through a $(cc-option)
> further down. We can safely remove the first instances.
>
> In fact, since the -mno-mmx and -mno-sse options were introduced
> simultaneous with the other two options in the $(cc-option) [according
> to http://www.gnu.org/software/gcc/gcc-3.1/changes.html], and since
> the former were unconditionally used, one can deduce that only gcc
> versions knowing about all four are supported. So also eliminate the
> $(cc-option) wrap.
>
> Signed-off-by: Rasmus Villemoes <linux@...musvillemoes.dk>

Acked-by: Peter Foley <pefoley2@...oley.com>
--
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/