Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751286AbdFDU1C (ORCPT ); Sun, 4 Jun 2017 16:27:02 -0400 Received: from outpost1.zedat.fu-berlin.de ([130.133.4.66]:58035 "EHLO outpost1.zedat.fu-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751177AbdFDU05 (ORCPT ); Sun, 4 Jun 2017 16:26:57 -0400 Subject: Re: sparc gcc 7.1 compile issue To: David Miller References: <1f8e2488-d051-7688-2d40-089f4acab6ce@physik.fu-berlin.de> <20170602.132809.1754806777743128355.davem@davemloft.net> <20170604.162150.706660537991026056.davem@davemloft.net> Cc: wbx@openadk.org, linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org From: John Paul Adrian Glaubitz Message-ID: Date: Sun, 4 Jun 2017 22:26:50 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170604.162150.706660537991026056.davem@davemloft.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Originating-IP: 93.193.85.89 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2240 Lines: 55 On 06/04/2017 10:21 PM, David Miller wrote: > It's the compiler. It's not compiling the kernel properly. What part > of that do you not understand? The kernel, if miscompiled itself, > cannot do anything about it. How do you know it's the compiler? This has not happened with earlier versions of the kernel using the same compiler. Again, we're not using gcc-7.1 > The kernel expects that the compiler is able to compile the kernel > properly. Period. I'm not arguing that. > I know this might in fact be news to you, but that is a pretty > fundamental expectation. And when the compiler has bugs, it will not > compile the kernel properly and therefore the kernel won't work. Again, how do you know it's the compiler? > Therefore the compiler in that situation needs to be fixed, not the > kernel. And furthermore, you are dealing wiht an unreleased version > of gcc which is stil under development, having lots of changes made, > bugs fixed, etc. It's a moving target. The kernel was not compiled with gcc-7.1. I *never* said that. We're not using Gentoo here, this is Debian. The kernel was compiled with the current stable gcc-6 version. > In my point of view if I have to choose between working on bugs > showing up in the kernel with released versions of gcc, vs unreleased > versions of gcc, due to time constraints. I will always put effort > into released versions of gcc. I don't understand why you keep bringing this up. I *never* said the kernel was built with gcc-7.1. It wasn't. > Why can't you understand this fundamental issue of my having > constraints like time? If you don't like this, find some other > person to fix your bug or even better, do it yourself you have > access to all of the code just like I or anyone else does. I don't understand why you're attacking me personally here when I'm pointing out an important issue with the kernel on SPARC. You're the person who is most knowledgeable with the code and the bug seems pretty darn serious. Hence I was reporting it. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@debian.org `. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913