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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B72B3C7EE24 for ; Sat, 3 Jun 2023 07:44:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233966AbjFCHoK (ORCPT ); Sat, 3 Jun 2023 03:44:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52614 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232017AbjFCHoG (ORCPT ); Sat, 3 Jun 2023 03:44:06 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DEF20E41 for ; Sat, 3 Jun 2023 00:44:04 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 69A4E60A64 for ; Sat, 3 Jun 2023 07:44:04 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 92FA4C433EF; Sat, 3 Jun 2023 07:44:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1685778243; bh=xYfWPnmqvmhHvjBtXOmu6oNPER75NycwsuL1memEjUU=; h=In-Reply-To:References:Date:From:To:Cc:Subject:From; b=Vyoliw2rtxHkj8drtwr2CbCjbrkVI5kMP2LGsErsIjUcLXk2HSBwEsC6z49M0ur/W aUNWbQwFXlDYvh9Cz8SvJdpoC67dvPwDRmkGeVL/I8QsLp5h3v5Zm0pdIoNZXmn4Zt O5BMuwVO8LXA+kLHNaOOaOzR79BUwkva/WOdAdr5PllF4Mcz+UFfAYUsmB6vgcFXT7 su+3gg8QOc1UiTwJfUjUgaEnO7RiqWo/Op2v5e4a8JQ59Vh8KwmBMmf6vRh+36J9rW nJHTclWEuC/q+dAwvpXP2SDFjBAyfJafEGYW0u33sXflfWQ4XfdZGX9o1DtZmo4HQj P8H4ng2AOipgw== Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailauth.nyi.internal (Postfix) with ESMTP id 7322E27C0054; Sat, 3 Jun 2023 03:44:02 -0400 (EDT) Received: from imap51 ([10.202.2.101]) by compute6.internal (MEProxy); Sat, 03 Jun 2023 03:44:02 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeelgedguddvhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdet rhhnugcuuegvrhhgmhgrnhhnfdcuoegrrhhnugeskhgvrhhnvghlrdhorhhgqeenucggtf frrghtthgvrhhnpedvveeigfetudegveeiledvgfevuedvgfetgeefieeijeejffeggeeh udegtdevheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpegrrhhnugdomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidquddvkeehudej tddvgedqvdekjedttddvieegqdgrrhhnugeppehkvghrnhgvlhdrohhrghesrghrnhgusg druggv X-ME-Proxy: Feedback-ID: i36794607:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 105D0B60086; Sat, 3 Jun 2023 03:44:02 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-447-ge2460e13b3-fm-20230525.001-ge2460e13 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20230417205447.1800912-1-arnd@kernel.org> <87ttwnnrer.fsf@kernel.org> <504c5a7d-0bfd-4b1e-a7f0-65d072657e0a@app.fastmail.com> <87mt2eoopo.fsf@kernel.org> Date: Sat, 03 Jun 2023 09:43:35 +0200 From: "Arnd Bergmann" To: "Arnd Bergmann" , "Kalle Valo" Cc: Netdev , linux-kernel@vger.kernel.org Subject: Re: [PATCH] wireless: ath: work around false-positive stringop-overread warning Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 8, 2023, at 17:07, Arnd Bergmann wrote: > On Mon, May 8, 2023, at 16:57, Kalle Valo wrote: >> With older GCC versions from your page I don't have this problem. I'm >> using Debian 10 still so so is my libc too old? > > (dropping most Cc) > > Indeed, thanks for the report, I forgot about that issue. I used > to build the cross toolchains in an old Ubuntu 16.04 chroot to avoid > that issue, and I linked all other dependencies statically. > > The gcc-13.1.0 builds are the first ones I did on an arm64 machine, > so I had to create a new build environment and started out with > just my normal Debian testing rootfs, which caused me enough issues > to figure out first. > > I had previously experimented with linking statically against > musl to avoid all other dependencies, but that ended up with > slower binaries because the default memory allocator in musl > doesn't work that well for gcc, and I never quite figured out > how to pick a different memory allocator, or which one to use. > > I should probably just pick an older Debian release that is new > enough to contain cross compilers for arm64 and x86 and then > set up the same kind of chroot I had in before. It took me a while, but now I have a working build setup in a Debian Buster schroot with gcc-13 as the main compiler, and I updated the gcc-13.1 binaries with those, as well as uploading gcc-11.4 and gcc-12.3 build the same way. I have only tested the binaries on arm64 Debian testing, could you see if the new x86 builds work for you? Arnd