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=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 3A04AC433DF for ; Sun, 11 Oct 2020 12:03:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E870920774 for ; Sun, 11 Oct 2020 12:03:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387726AbgJKMDR (ORCPT ); Sun, 11 Oct 2020 08:03:17 -0400 Received: from gate.crashing.org ([63.228.1.57]:44423 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387690AbgJKMDR (ORCPT ); Sun, 11 Oct 2020 08:03:17 -0400 X-Greylist: delayed 3327 seconds by postgrey-1.27 at vger.kernel.org; Sun, 11 Oct 2020 08:03:16 EDT Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 09BB4NkW006661; Sun, 11 Oct 2020 06:04:24 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 09BB4Kuw006658; Sun, 11 Oct 2020 06:04:20 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Sun, 11 Oct 2020 06:04:20 -0500 From: Segher Boessenkool To: Mark Wielaard Cc: Andi Kleen , Peter Zijlstra , Stephane Eranian , linux-toolchains@vger.kernel.org, Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, Ingo Molnar , Jiri Olsa , Namhyung Kim , Ian Rogers , "Phillips, Kim" , Mark Rutland , Masami Hiramatsu Subject: Re: Additional debug info to aid cacheline analysis Message-ID: <20201011110420.GO2672@gate.crashing.org> References: <20201006131703.GR2628@hirez.programming.kicks-ass.net> <20201008070231.GS2628@hirez.programming.kicks-ass.net> <50338de81b34031db8637337f08b89b588476211.camel@klomp.org> <20201008212259.gdhlwdswn5pu4zos@two.firstfloor.org> <20201010205836.GA2666@wildebeest.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201010205836.GA2666@wildebeest.org> User-Agent: Mutt/1.4.2.3i Precedence: bulk List-ID: X-Mailing-List: linux-toolchains@vger.kernel.org Hi! On Sat, Oct 10, 2020 at 10:58:36PM +0200, Mark Wielaard wrote: > On Thu, Oct 08, 2020 at 02:23:00PM -0700, Andi Kleen wrote: > > So I guess could disable it for 5.0+ only. > > Yes, that would work. I don't know what the lowest supported GCC > version is, but technically it was definitely fixed in 4.10.0, 4.8.4 > and 4.9.2. Fwiw, GCC 4.10 was renamed to GCC 5 before it was released (it was the first release with the new version number scheme). Only old development versions (that no one should use) identify as 4.10. > And various distros would probably have backported the > fix. But checking for 5.0+ would certainly give you a good version. Yes, esp. since some versions of 4.9 and 4.8 are still buggy. No one should use any version for which a newer bug-fix release has long been available, but do you want to deal with bugs from people who do not? Segher