From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 108A4C433E6 for ; Thu, 14 Jan 2021 08:19:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B8B02239EB for ; Thu, 14 Jan 2021 08:19:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728075AbhANITA (ORCPT ); Thu, 14 Jan 2021 03:19:00 -0500 Received: from mail.kernel.org ([198.145.29.99]:60892 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726677AbhANIS7 (ORCPT ); Thu, 14 Jan 2021 03:18:59 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 59A76239EF for ; Thu, 14 Jan 2021 08:18:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1610612299; bh=N5a/atXasUevjqMzJiK/W4ty6kZ/4vCWt3gzActcTYg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=mjy6JA9jSp5PfOvVAi+GvjeqdW/DO59+DyAwcGONOdCYfddZ9U0BRXguQ63inG7B3 V9D2wta4Qtl8EtjRvAiRUnqgpVXdtR8crp0+QSC/YfnI1PHiJHjbMWwbAHTXQad3iM wD5DhEhTrYjPfGPQkK0JcYaK1Jv2yq5244F1j7LFlhOCnVwOSQiFydufTRzPr2qHxr mwSWA4ulBIZA3DqN8+IuNc7/z4qDQnNjquw7C2HLjm2onsjlLUBmQco/ZtdTcpGLY1 tVVcGCM9vnQelSg3rXF+zk61G9nGj6H84cAbke7hsgwT5DcvssQikdmtnvCjl18N4C xgr3r8uTCTWQQ== Received: by mail-oo1-f46.google.com with SMTP id x203so1185647ooa.9 for ; Thu, 14 Jan 2021 00:18:19 -0800 (PST) X-Gm-Message-State: AOAM5317KmmrOQdOMlfbN71AuJlvOOnHwijI8VV8I/GZEemKIKcK8rr4 /qvaxuEmQsUct50+MslyY4XjTZu/RODqHaxvns0= X-Google-Smtp-Source: ABdhPJzx8azhVF1beD/V0rXaIBuAZoNnC2aHwFxMLkKAVC5qCL4dJBDnifu5IYM1MfZXDwuJ0FTcRUp6xtCPtx/OeUg= X-Received: by 2002:a05:6820:41:: with SMTP id v1mr3970890oob.41.1610612298532; Thu, 14 Jan 2021 00:18:18 -0800 (PST) MIME-Version: 1.0 References: <20210112224832.10980-1-will@kernel.org> <161055398865.21762.12236232732054213928.b4-ty@arm.com> <20210113214436.GL1551@shell.armlinux.org.uk> In-Reply-To: From: Ard Biesheuvel Date: Thu, 14 Jan 2021 09:18:07 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64 To: Linus Torvalds Cc: Russell King - ARM Linux admin , Florian Weimer , Arnd Bergmann , "Cc: Android Kernel" , "Theodore Ts'o" , Peter Zijlstra , Catalin Marinas , Masahiro Yamada , Nick Desaulniers , Linux Kernel Mailing List , Will Deacon , linux-arm-kernel Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 13 Jan 2021 at 23:09, Linus Torvalds wrote: > > On Wed, Jan 13, 2021 at 1:44 PM Russell King - ARM Linux admin > wrote: > > > > So, maybe the Sparc issue was just a similar but different bug in gcc > > 4.9.x. > > Good catch. And I know this bug has happened independently on > different architectures several times (I remember this on x86-64 as > well), so I started looking around. > > And in fact, 4.9 was buggy on x86-64 too: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 > > And yeah, _that_ gcc bug wasn't actually x86-64 specific, but > apparently a generic instruction scheduling bug. > > So it's an independent bug, but I do have to admit that the arguments > against 4.9 are piling up (even if that particular fix apparently got > fixed in the gcc branches and apparently backported to distro > compilers too). > So if the arguments are piling up, what is holding us back, other than inertia? RHEL 7 used to be a factor, but it ships with 4.8 not 4.9, so its users already need to upgrade. Is anyone aware of a good reason to keep 4.9 supported? Are any other long term supported distros using 4.9.x? I know that distros probably backported fixes for all of these issues, but without a way to interrogate the compiler about this, that doesn't really make a difference IMHO. Note that banning 4.9 for arm64 and banning it in general should be two different changes in any case, as the former will need to be backported to -stable kernels as well. -- Ard. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B0D42C433DB for ; Thu, 14 Jan 2021 08:19:56 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4E7DD2343F for ; Thu, 14 Jan 2021 08:19:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4E7DD2343F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=vPLX5aaq44ZKKf0hXGjlIk8N1XGaCM2qnmmmqubEIoU=; b=0xCddqz53qa7sSnVymMAQjams bS3WbKKijvTIch+EXgGknTj+6q7V6gD7/ySlhhzyEFg8zfBVaCMEbtsl1JNYaCgcdOPx+zD6Slnef /KHgzF+cVDBRanb3CsTemfj6OGUPPwqqMaaxbRtFFR8qtBNU7SO4/k1F6vtd7gvo4caMSr6ZaOrBL xHGmk9p8uWOBsE1cW0soVj7LcaoqL7Ne5t37w5Pyw0loGJ45RKPGciKx5JrfDuhyrQyHvRJj2wQGO 2pAhO50Crr8tc5DbDDLuejF2vnMMGF3BBlJod2aNoXPyIQIObNMR1LTcvTjmMK7WZ0w5fKYgj08gO ZAPqoasHQ==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kzxpn-0005wv-0g; Thu, 14 Jan 2021 08:18:23 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kzxpk-0005w9-3x for linux-arm-kernel@lists.infradead.org; Thu, 14 Jan 2021 08:18:21 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id 48A06233FD for ; Thu, 14 Jan 2021 08:18:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1610612299; bh=N5a/atXasUevjqMzJiK/W4ty6kZ/4vCWt3gzActcTYg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=mjy6JA9jSp5PfOvVAi+GvjeqdW/DO59+DyAwcGONOdCYfddZ9U0BRXguQ63inG7B3 V9D2wta4Qtl8EtjRvAiRUnqgpVXdtR8crp0+QSC/YfnI1PHiJHjbMWwbAHTXQad3iM wD5DhEhTrYjPfGPQkK0JcYaK1Jv2yq5244F1j7LFlhOCnVwOSQiFydufTRzPr2qHxr mwSWA4ulBIZA3DqN8+IuNc7/z4qDQnNjquw7C2HLjm2onsjlLUBmQco/ZtdTcpGLY1 tVVcGCM9vnQelSg3rXF+zk61G9nGj6H84cAbke7hsgwT5DcvssQikdmtnvCjl18N4C xgr3r8uTCTWQQ== Received: by mail-oo1-f43.google.com with SMTP id j8so1199661oon.3 for ; Thu, 14 Jan 2021 00:18:19 -0800 (PST) X-Gm-Message-State: AOAM532wTTx+xWMakKfrBJf0HKdgUgIA2IUCbu12TNBkuOz2wrJw5/zz OAuTrngfcpnEJ8QVCFAYjV/4B40isbuj9g5BCkw= X-Google-Smtp-Source: ABdhPJzx8azhVF1beD/V0rXaIBuAZoNnC2aHwFxMLkKAVC5qCL4dJBDnifu5IYM1MfZXDwuJ0FTcRUp6xtCPtx/OeUg= X-Received: by 2002:a05:6820:41:: with SMTP id v1mr3970890oob.41.1610612298532; Thu, 14 Jan 2021 00:18:18 -0800 (PST) MIME-Version: 1.0 References: <20210112224832.10980-1-will@kernel.org> <161055398865.21762.12236232732054213928.b4-ty@arm.com> <20210113214436.GL1551@shell.armlinux.org.uk> In-Reply-To: From: Ard Biesheuvel Date: Thu, 14 Jan 2021 09:18:07 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64 To: Linus Torvalds X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210114_031820_382649_8E8BA622 X-CRM114-Status: GOOD ( 18.35 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Florian Weimer , Arnd Bergmann , Theodore Ts'o , Will Deacon , Peter Zijlstra , Catalin Marinas , Masahiro Yamada , Nick Desaulniers , Russell King - ARM Linux admin , Linux Kernel Mailing List , "Cc: Android Kernel" , linux-arm-kernel Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, 13 Jan 2021 at 23:09, Linus Torvalds wrote: > > On Wed, Jan 13, 2021 at 1:44 PM Russell King - ARM Linux admin > wrote: > > > > So, maybe the Sparc issue was just a similar but different bug in gcc > > 4.9.x. > > Good catch. And I know this bug has happened independently on > different architectures several times (I remember this on x86-64 as > well), so I started looking around. > > And in fact, 4.9 was buggy on x86-64 too: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 > > And yeah, _that_ gcc bug wasn't actually x86-64 specific, but > apparently a generic instruction scheduling bug. > > So it's an independent bug, but I do have to admit that the arguments > against 4.9 are piling up (even if that particular fix apparently got > fixed in the gcc branches and apparently backported to distro > compilers too). > So if the arguments are piling up, what is holding us back, other than inertia? RHEL 7 used to be a factor, but it ships with 4.8 not 4.9, so its users already need to upgrade. Is anyone aware of a good reason to keep 4.9 supported? Are any other long term supported distros using 4.9.x? I know that distros probably backported fixes for all of these issues, but without a way to interrogate the compiler about this, that doesn't really make a difference IMHO. Note that banning 4.9 for arm64 and banning it in general should be two different changes in any case, as the former will need to be backported to -stable kernels as well. -- Ard. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel