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 56093EB64D7 for ; Wed, 21 Jun 2023 00:13:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229796AbjFUANW (ORCPT ); Tue, 20 Jun 2023 20:13:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42012 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229595AbjFUANU (ORCPT ); Tue, 20 Jun 2023 20:13:20 -0400 Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C537A172C for ; Tue, 20 Jun 2023 17:13:18 -0700 (PDT) Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-6686ef86110so1912949b3a.2 for ; Tue, 20 Jun 2023 17:13:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20221208.gappssmtp.com; s=20221208; t=1687306398; x=1689898398; h=message-id:to:from:cc:in-reply-to:subject:date:from:to:cc:subject :date:message-id:reply-to; bh=tjYx1i3/gCVvDUNwYH2uVhDCA+CPehZaUiYWjawRZkM=; b=sjUoX7jwC00g/1eLiAyZp7jtN9jgrMFgXJTIjzmMqeBGF6gNt7yEtIuDKhS6YWSKNw iG3jzjNxjTLdWROYuSIsCCK5Maghmyppas9yOrDKWiIaVNWLL8PGlYlojeJZXG3Jk+CR 7M+80O9YfMnNcFB49lEcYcCFQMKY0lO8WrimTAdT6vcGiFhlfStGWkpJCFFhAQ0hV53e BKC4XRy/AvZKKysP4pFfNc0K1titJwvX4ea3CK9UxOef+Jt3oHPs2QQOG3WmUSJXRVfR eFeaVHM/mea84txT62UN5B3oJOxi/WHB9wJ15z8+3tCVqDhglOdrEL+0hOKbMZvN1Hgy TDxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687306398; x=1689898398; h=message-id:to:from:cc:in-reply-to:subject:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=tjYx1i3/gCVvDUNwYH2uVhDCA+CPehZaUiYWjawRZkM=; b=YWSjQbbbUMR/9BSDcEW6KA1fP9uljE1zShXsO8ii3Jhx/n/OML7MuTSxgxWpoxOZal DHeZr4SSTPmMtwySWs0mkBQn5T0FEHiePevReufRY9gfKGjN4xEpgeWy2DWyPQN8eboj GcAD5c5nnSBuN3r9LEEP6bEBw/hFnv+BTuUutP2UV563BsI3k2HtA9hWMZSGgwJ7ng6x iFJTvmYeaLLYjIOkhgN6+Zc/6p59ah5N0FENtLqK2ZtlC5ozOzpNfjvl2PkHIyc48/+v CTqf2QC96kIAFVQTD6ysHb9YxoWzynDFt1Ntg/9NsMrtkksZTp/LdAUIxOkhulULuW12 ZDmw== X-Gm-Message-State: AC+VfDywgck6TU9t5fwQ2jO4i9BeQPptkWXUDV6nKQ8uYYC1dNWXDdUb fvOg6BgfJlxHUK0qrxFRLBzmr3TYEKHMgcJXEZo= X-Google-Smtp-Source: ACHHUZ7Nw4aRq+TWO1VkY0DHqMW34dcaoaGD141nBeA4rU0iyYuaxNlQebBEStDo9kJp5JEvtCc1yA== X-Received: by 2002:a05:6a20:5493:b0:122:9af9:67c with SMTP id i19-20020a056a20549300b001229af9067cmr3139865pzk.23.1687306398159; Tue, 20 Jun 2023 17:13:18 -0700 (PDT) Received: from localhost ([50.221.140.188]) by smtp.gmail.com with ESMTPSA id bm17-20020a056a00321100b0064ccfb73cb8sm1804052pfb.46.2023.06.20.17.13.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Jun 2023 17:13:17 -0700 (PDT) Date: Tue, 20 Jun 2023 17:13:17 -0700 (PDT) X-Google-Original-Date: Tue, 20 Jun 2023 17:12:37 PDT (-0700) Subject: Re: [PATCH v2 0/4] riscv: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATION In-Reply-To: CC: Conor Dooley , jszhang@kernel.org, llvm@lists.linux.dev, Paul Walmsley , aou@eecs.berkeley.edu, Arnd Bergmann , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org From: Palmer Dabbelt To: ndesaulniers@google.com Message-ID: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 20 Jun 2023 14:08:33 PDT (-0700), Palmer Dabbelt wrote: > On Tue, 20 Jun 2023 13:47:07 PDT (-0700), ndesaulniers@google.com wrote: >> On Tue, Jun 20, 2023 at 4:41 PM Palmer Dabbelt wrote: >>> >>> On Tue, 20 Jun 2023 13:32:32 PDT (-0700), ndesaulniers@google.com wrote: >>> > On Tue, Jun 20, 2023 at 4:13 PM Conor Dooley wrote: >>> >> >>> >> On Tue, Jun 20, 2023 at 04:05:55PM -0400, Nick Desaulniers wrote: >>> >> > On Mon, Jun 19, 2023 at 6:06 PM Palmer Dabbelt wrote: >>> >> > > On Thu, 15 Jun 2023 06:54:33 PDT (-0700), Palmer Dabbelt wrote: >>> >> > > > On Wed, 14 Jun 2023 09:25:49 PDT (-0700), jszhang@kernel.org wrote: >>> >> > > >> On Wed, Jun 14, 2023 at 07:49:17AM -0700, Palmer Dabbelt wrote: >>> >> > > >>> On Tue, 23 May 2023 09:54:58 PDT (-0700), jszhang@kernel.org wrote: >>> >> >>> >> > > >> Commit 3b90b09af5be ("riscv: Fix orphan section warnings caused by >>> >> > > >> kernel/pi") touches vmlinux.lds.S, so to make the merge easy, this >>> >> > > >> series is based on 6.4-rc2. >>> >> > > > >>> >> > > > Thanks. >>> >> > > >>> >> > > Sorry to be so slow here, but I think this is causing LLD to hang on >>> >> > > allmodconfig. I'm still getting to the bottom of it, there's a few >>> >> > > other things I have in flight still. >>> >> > >>> >> > Confirmed with v3 on mainline (linux-next is pretty red at the moment). >>> >> > https://lore.kernel.org/linux-riscv/20230517082936.37563-1-falcon@tinylab.org/ >>> >> >>> >> Just FYI Nick, there's been some concurrent work here from different >>> >> people working on the same thing & the v3 you linked (from Zhangjin) was >>> >> superseded by this v2 (from Jisheng). >>> > >>> > Ah! I've been testing the deprecated patch set, sorry I just looked on >>> > lore for "dead code" on riscv-linux and grabbed the first thread, >>> > without noticing the difference in authors or new version numbers for >>> > distinct series. ok, nevermind my noise. I'll follow up with the >>> > correct patch set, sorry! >>> >>> Ya, I hadn't even noticed the v3 because I pretty much only look at >>> patchwork these days. Like we talked about in IRC, I'm going to go test >>> the merge of this one and see what's up -- I've got it staged at >>> , >>> though that won't be a stable hash if it's actually broken... >> >> Ok, https://lore.kernel.org/linux-riscv/20230523165502.2592-1-jszhang@kernel.org/ >> built for me. If you're seeing a hang, please let me know what >> version of LLD you're using and I'll build that tag from source to see >> if I can reproduce, then bisect if so. >> >> $ ARCH=riscv LLVM=1 /usr/bin/time -v make -j128 allmodconfig vmlinux >> ... >> Elapsed (wall clock) time (h:mm:ss or m:ss): 2:35.68 >> ... >> >> Tested-by: Nick Desaulniers # build > > OK, it triggered enough of a rebuild that it might take a bit for > anything to filter out. I'm on LLVM 16.0.2 $ git describe llvmorg-16.0.2 $ git log | head -n1 commit 18ddebe1a1a9bde349441631365f0472e9693520 that seems to hang for me -- or at least run for an hour without completing, so I assume it's hung. I'm not wed to 16.0.2, it just happens to be the last time I bumped the toolchain. I'm moving to 16.0.5 to see if that changes anything. > > Thanks! > >> >>> >>> > >>> >> >>> >> Cheers, >>> >> Conor. >>> > >>> > >>> > >>> > -- >>> > Thanks, >>> > ~Nick Desaulniers >> >> >> >> -- >> Thanks, >> ~Nick Desaulniers