Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S945712AbcJSQBv (ORCPT ); Wed, 19 Oct 2016 12:01:51 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:35396 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936118AbcJSQBg (ORCPT ); Wed, 19 Oct 2016 12:01:36 -0400 MIME-Version: 1.0 In-Reply-To: <20161019155658.GB4411@x4> References: <20161017183806.GG5601@arm.com> <20161019153746.GA4411@x4> <20161019155658.GB4411@x4> From: Linus Torvalds Date: Wed, 19 Oct 2016 09:01:33 -0700 X-Google-Sender-Auth: b7juSV_dkLdg8VfhqbIyMIGVI6g Message-ID: Subject: Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness To: Markus Trippelsdorf Cc: Will Deacon , "linux-arm-kernel@lists.infradead.org" , Linux Kernel Mailing List , Peter Zijlstra , Ingo Molnar , Ard Biesheuvel , james.greenhalgh@arm.com, Gregory Clement , Stephen Boyd Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 783 Lines: 20 On Wed, Oct 19, 2016 at 8:56 AM, Markus Trippelsdorf wrote: > On 2016.10.19 at 08:55 -0700, Linus Torvalds wrote: >> >> Well, in the meantime we apparently have to live with it. Unless Will >> is using some unreleased gcc version that nobody else is using and we >> can just ignore it? > > Yes, he is using gcc-7 that is unreleased. (It will be released April > next year.) Ahh, self-built? So it's not part of some experimental ARM distro setup and this will be annoying lots of people? If so, still think that we could just get rid of the ____ilog2_NaN() thing as it's not _that_ important, but it's certainly not very high-priority. Will can do it in his tree too for testing, and it can remind people to get the gcc problem fixed. Linus