From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9668C3822A0; Fri, 13 Mar 2026 21:17:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773436643; cv=none; b=B/1f/vU0CAqyUs9XYAXypMyrDgqjZF90U9UY9Jrt1yJXYrdPZzitmKoYfEFcnFUjD2k3f4Z9s8xZGm+tATAQ7QSXZuvjds1CxiX8XT87wq7ygq63y8NzXfyAlmRt5Iv2smrJHjV9sveLGF5bsRus+9oPslhibpF/gJKE9ptFEJY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773436643; c=relaxed/simple; bh=myel91aE8wQs1det+Z6kH8GZ8AHOc1SqZetl9raqle4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=nJThHaZgPKqXOMqsAzHEdDyemKBHt4+fcuy4yyatyY51plDY0R9scZGhu7duhoqszEfvbf//HEFdEAXmesF0/sVL2SJcKBxnAq7ovqj3jb6bNZyHon3hgnBifG7+y2SGog16dw/1wnRjTEFIJoFLTozmVagnlD9EihtpzMO70as= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=CIBUics/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CIBUics/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A5101C19421; Fri, 13 Mar 2026 21:17:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773436643; bh=myel91aE8wQs1det+Z6kH8GZ8AHOc1SqZetl9raqle4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CIBUics/X+9NcGHEF4KwWAo4oPdMnhsLssS5FzDYauWU1X1YT3jWDWViommnyL9F4 eZ9kLO9xZQ1bGDOs/23yJMl/H+KZ8kn1WNmXKgAGE9Ol3hUjIVhIbrt3JhrpWTL7sm PFxIbQraVme01U06mtVV8TcilvUSP5WLwD7UAgnTQTrZ3Tk82r3g1Y9qmrHz0TD1Fe bgpAYFqWYV2TmfqTmVZXxE+ejiU4Xs682uBUZ37+cQSHYVT4xv4/GR9IGo/o1VntXi 7eoPqB7xSHFCaePviJQCRKuiYrUDMdUOZPtUaTqawVy4GS/PskpseCEapUu2NCHCja hcKvHsPTCbaDg== Date: Fri, 13 Mar 2026 14:17:21 -0700 From: Namhyung Kim To: Ian Rogers Cc: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Adrian Hunter , Kan Liang , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, Eric Biggers Subject: Re: [PATCH v1] perf build: Revert "enable -fno-strict-aliasing" Message-ID: References: <20250904174430.1414548-1-irogers@google.com> <20250904204117.GC4067720@noisy.programming.kicks-ass.net> <20250904205924.GO4068168@noisy.programming.kicks-ass.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Thu, Mar 12, 2026 at 01:58:31PM -0700, Ian Rogers wrote: > On Thu, Sep 4, 2025 at 2:33 PM Ian Rogers wrote: > > Anyway, the intent with adding -fno-strict-aliasing was that it was > > temporary as part of removing the libcrypto dependency and when the > > unaligned code landed we'd do this revert. I don't remember what's going on here but as it's not there originally, I think we can revert to the change for now. But it doesn't apply, care to rebase? Thanks, Namhyung