Message ID | 20221014204210.383380-1-nathan@kernel.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4ac7:0:0:0:0:0 with SMTP id y7csp370502wrs; Fri, 14 Oct 2022 13:49:09 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4XhUjWbLhBLMrKiV9OTeeXq3YYo6e7mjQqwyHeRmKYSVmmb774QEB2aYVgOb9CDT10kyo9 X-Received: by 2002:a17:906:8a47:b0:78d:b6d8:f531 with SMTP id gx7-20020a1709068a4700b0078db6d8f531mr4918004ejc.287.1665780549161; Fri, 14 Oct 2022 13:49:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665780549; cv=none; d=google.com; s=arc-20160816; b=cYEA1H+P5O5eH8F8qgCgNFaCMhOf6MqUsDpYRVK3ZaUoLbQRCaRyfK/997EoZIl0ny xsQRnAS78CwpabLRb8RPoq/0RmAsnrNeyflevPhmE/6FdBGoW5qeyS8aqRmgUir6NyIx AZGPzMzEgAxh5sKgclBAKOVscMaGZYi9yXeygV224UdFx4wVxx77Idx74xurm6JRxMcp ONJ51XRiCd1A58XTIuaWLg121xV4Xxv0vDa4Zdmz4UZW34FTHei3RCcLesmVk3ByE/LL 4d3ReL60rA+Lzz/c36bcbNCHigR/K/6zzjUqPeeDyr3xdS6bqxQIm5tLNOtGUrB1TGDn Vzxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=7z024cK9PlBiUPQ7BSW/g4loV+fhLNOSOI1q8+h7S/c=; b=LEx+fqFaaSg5jIeYt24mW0OUNWPzuiEwBQXOTdSo0Z9YNZ0iEZDV5x1GkTuHiftgLk zSYuBLbPEsLbG58Ww5vJjlFfpno7Ml2O6AE5DwniFCT9aiI2Yeqmq8TQY1eBxKtJvvCS odL1EYXDkLfAEzXtvlB6UO3Gdi1Esm0mCCLfGha+8SSM1Gq9lWSToLZgf7ylnYGtR1mG uXO6Z+q2LdUL2FTn7KXi7H1b0VsaIvRAIRbsPV3inM8uQ+P7Fiyg3e42P5JLnn/qLvg/ x52DnJcwNyMhiFLwcqJLSaBeSh/QWnPh8QpAnoUS/R1QCyt2Ar6xrqEDd181TYZqEKSS jq2w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=pJdQ+TDx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id sg20-20020a170907a41400b0078cc8a2cf4bsi3320277ejc.614.2022.10.14.13.48.44; Fri, 14 Oct 2022 13:49:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=pJdQ+TDx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231558AbiJNUsV (ORCPT <rfc822;ouuuleilei@gmail.com> + 99 others); Fri, 14 Oct 2022 16:48:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45784 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231526AbiJNUsS (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 14 Oct 2022 16:48:18 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E39481ACABB; Fri, 14 Oct 2022 13:48:15 -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 ams.source.kernel.org (Postfix) with ESMTPS id 74554B82421; Fri, 14 Oct 2022 20:48:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 60012C433D7; Fri, 14 Oct 2022 20:48:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1665780493; bh=C3fOH2Mc8DRWmLYpWhPGyuj4dAcW5kYVpSBvOUxOFQc=; h=From:To:Cc:Subject:Date:From; b=pJdQ+TDxYwMeWzyEJyOKQ5BBV7ferow6GiaZchv9FWLdvRFrEENkmGWbNI5VhI9bZ QLEBqI3IDlO1DXZiVCzavpUqsRVOpOUJ4xN7SYmSBjY2vKx1N6wRTFZpeCKCpt3QWM MS9lRqcCaFCLrPizqRwI/wM+FNAJM+G8tpYP0AB4V8roJSuVicX095kjfB1qLmYIrM f0VMKqzxb90LlGeTyyckFIwNSqUSNrizHWqiJAve0tygFODyI0vZGfzgRUvaxeqDla lk/i63GdyfprtGwB8flJkDu7+uKY/v3bMn3c3jpHZFiLZ44xURS2ryrya4R2kpvhiP OgjlJzPY9Sp+Q== From: Nathan Chancellor <nathan@kernel.org> To: Andrew Morton <akpm@linux-foundation.org>, Masahiro Yamada <masahiroy@kernel.org> Cc: Nick Desaulniers <ndesaulniers@google.com>, Tom Rix <trix@redhat.com>, Palmer Dabbelt <palmer@dabbelt.com>, Conor Dooley <conor@kernel.org>, linux-kbuild@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, patches@lists.linux.dev, llvm@lists.linux.dev, Nathan Chancellor <nathan@kernel.org> Subject: [PATCH v2] lib/Kconfig.debug: Add check for non-constant .{s,u}leb128 support to DWARF5 Date: Fri, 14 Oct 2022 13:42:11 -0700 Message-Id: <20221014204210.383380-1-nathan@kernel.org> X-Mailer: git-send-email 2.38.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1746697505384109144?= X-GMAIL-MSGID: =?utf-8?q?1746697505384109144?= |
Series |
[v2] lib/Kconfig.debug: Add check for non-constant .{s,u}leb128 support to DWARF5
|
|
Commit Message
Nathan Chancellor
Oct. 14, 2022, 8:42 p.m. UTC
When building with a RISC-V kernel with DWARF5 debug info using clang
and the GNU assembler, several instances of the following error appear:
/tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported
Dumping the .s file reveals these .uleb128 directives come from
.debug_loc and .debug_ranges:
.Ldebug_loc0:
.byte 4 # DW_LLE_offset_pair
.uleb128 .Lfunc_begin0-.Lfunc_begin0 # starting offset
.uleb128 .Ltmp1-.Lfunc_begin0 # ending offset
.byte 1 # Loc expr size
.byte 90 # DW_OP_reg10
.byte 0 # DW_LLE_end_of_list
.Ldebug_ranges0:
.byte 4 # DW_RLE_offset_pair
.uleb128 .Ltmp6-.Lfunc_begin0 # starting offset
.uleb128 .Ltmp27-.Lfunc_begin0 # ending offset
.byte 4 # DW_RLE_offset_pair
.uleb128 .Ltmp28-.Lfunc_begin0 # starting offset
.uleb128 .Ltmp30-.Lfunc_begin0 # ending offset
.byte 0 # DW_RLE_end_of_list
There is an outstanding binutils issue to support a non-constant operand
to .sleb128 and .uleb128 in GAS for RISC-V but there does not appear to
be any movement on it, due to concerns over how it would work with
linker relaxation.
To avoid these build errors, prevent DWARF5 from being selected when
using clang and an assembler that does not have support for these symbol
deltas, which can be easily checked in Kconfig with as-instr plus the
small test program from the dwz test suite from the binutils issue.
Link: https://sourceware.org/bugzilla/show_bug.cgi?id=27215
Link: https://github.com/ClangBuiltLinux/linux/issues/1719
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
---
v2:
- Rebase on commit bb1435f3f575 ("Kconfig.debug: add toolchain
checks for DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT") from the kbuild
tree.
- Limit CONFIG_AS_HAS_NON_CONST_LEB128 dependency to GNU as. There
is no point to applying this dependency to the integrated
assembler because it will always pass.
- Apply the CONFIG_AS_HAS_NON_CONST_LEB128 dependency to
CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as well, due to the
aforementioned kbuild change.
- Move comment block to above CONFIG_AS_HAS_NON_CONST_LEB128, as the
configuration is now used in two places.
- Drop Conor's tested by, as the patch is different enough to
potentially require new testing.
v1: https://lore.kernel.org/20220928182523.3105953-1-nathan@kernel.org/
lib/Kconfig.debug | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
base-commit: bb1435f3f575b5213eaf27434efa3971f51c01de
Comments
On Fri, Oct 14, 2022 at 1:48 PM Nathan Chancellor <nathan@kernel.org> wrote: > > When building with a RISC-V kernel with DWARF5 debug info using clang > and the GNU assembler, several instances of the following error appear: > > /tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported > > Dumping the .s file reveals these .uleb128 directives come from > .debug_loc and .debug_ranges: > > .Ldebug_loc0: > .byte 4 # DW_LLE_offset_pair > .uleb128 .Lfunc_begin0-.Lfunc_begin0 # starting offset > .uleb128 .Ltmp1-.Lfunc_begin0 # ending offset > .byte 1 # Loc expr size > .byte 90 # DW_OP_reg10 > .byte 0 # DW_LLE_end_of_list > > .Ldebug_ranges0: > .byte 4 # DW_RLE_offset_pair > .uleb128 .Ltmp6-.Lfunc_begin0 # starting offset > .uleb128 .Ltmp27-.Lfunc_begin0 # ending offset > .byte 4 # DW_RLE_offset_pair > .uleb128 .Ltmp28-.Lfunc_begin0 # starting offset > .uleb128 .Ltmp30-.Lfunc_begin0 # ending offset > .byte 0 # DW_RLE_end_of_list > > There is an outstanding binutils issue to support a non-constant operand > to .sleb128 and .uleb128 in GAS for RISC-V but there does not appear to > be any movement on it, due to concerns over how it would work with > linker relaxation. > > To avoid these build errors, prevent DWARF5 from being selected when > using clang and an assembler that does not have support for these symbol > deltas, which can be easily checked in Kconfig with as-instr plus the > small test program from the dwz test suite from the binutils issue. > > Link: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > Link: https://github.com/ClangBuiltLinux/linux/issues/1719 > Signed-off-by: Nathan Chancellor <nathan@kernel.org> Thanks for keeping these LLVM_IAS=0 builds alive a little longer. My hope is the GNU binutils can relax their requirement for debug info sections to improve support for DWARF v5. Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> > --- > > v2: > - Rebase on commit bb1435f3f575 ("Kconfig.debug: add toolchain > checks for DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT") from the kbuild > tree. > - Limit CONFIG_AS_HAS_NON_CONST_LEB128 dependency to GNU as. There > is no point to applying this dependency to the integrated > assembler because it will always pass. > - Apply the CONFIG_AS_HAS_NON_CONST_LEB128 dependency to > CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as well, due to the > aforementioned kbuild change. > - Move comment block to above CONFIG_AS_HAS_NON_CONST_LEB128, as the > configuration is now used in two places. > - Drop Conor's tested by, as the patch is different enough to > potentially require new testing. > > v1: https://lore.kernel.org/20220928182523.3105953-1-nathan@kernel.org/ > > lib/Kconfig.debug | 9 +++++++-- > 1 file changed, 7 insertions(+), 2 deletions(-) > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index db8d9271cabf..5c1c63575895 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -231,6 +231,11 @@ config DEBUG_INFO > in the "Debug information" choice below, indicating that debug > information will be generated for build targets. > > +# Clang is known to generate .{s,u}leb128 with symbol deltas with DWARF5, which > +# some targets may not support: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > +config AS_HAS_NON_CONST_LEB128 > + def_bool $(as-instr,.uleb128 .Lexpr_end4 - .Lexpr_start3\n.Lexpr_start3:\n.Lexpr_end4:) > + > choice > prompt "Debug information" > depends on DEBUG_KERNEL > @@ -253,7 +258,7 @@ config DEBUG_INFO_NONE > config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT > bool "Rely on the toolchain's implicit default DWARF version" > select DEBUG_INFO > - depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502) > + depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > help > The implicit default version of DWARF debug info produced by a > toolchain changes over time. > @@ -277,7 +282,7 @@ config DEBUG_INFO_DWARF4 > config DEBUG_INFO_DWARF5 > bool "Generate DWARF Version 5 debuginfo" > select DEBUG_INFO > - depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502) > + depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > help > Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc > 5.0+ accepts the -gdwarf-5 flag but only had partial support for some > > base-commit: bb1435f3f575b5213eaf27434efa3971f51c01de > -- > 2.38.0 > -- Thanks, ~Nick Desaulniers
On Sat, Oct 15, 2022 at 6:52 AM Nick Desaulniers <ndesaulniers@google.com> wrote: > > On Fri, Oct 14, 2022 at 1:48 PM Nathan Chancellor <nathan@kernel.org> wrote: > > > > When building with a RISC-V kernel with DWARF5 debug info using clang > > and the GNU assembler, several instances of the following error appear: > > > > /tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported > > > > Dumping the .s file reveals these .uleb128 directives come from > > .debug_loc and .debug_ranges: > > > > .Ldebug_loc0: > > .byte 4 # DW_LLE_offset_pair > > .uleb128 .Lfunc_begin0-.Lfunc_begin0 # starting offset > > .uleb128 .Ltmp1-.Lfunc_begin0 # ending offset > > .byte 1 # Loc expr size > > .byte 90 # DW_OP_reg10 > > .byte 0 # DW_LLE_end_of_list > > > > .Ldebug_ranges0: > > .byte 4 # DW_RLE_offset_pair > > .uleb128 .Ltmp6-.Lfunc_begin0 # starting offset > > .uleb128 .Ltmp27-.Lfunc_begin0 # ending offset > > .byte 4 # DW_RLE_offset_pair > > .uleb128 .Ltmp28-.Lfunc_begin0 # starting offset > > .uleb128 .Ltmp30-.Lfunc_begin0 # ending offset > > .byte 0 # DW_RLE_end_of_list > > > > There is an outstanding binutils issue to support a non-constant operand > > to .sleb128 and .uleb128 in GAS for RISC-V but there does not appear to > > be any movement on it, due to concerns over how it would work with > > linker relaxation. > > > > To avoid these build errors, prevent DWARF5 from being selected when > > using clang and an assembler that does not have support for these symbol > > deltas, which can be easily checked in Kconfig with as-instr plus the > > small test program from the dwz test suite from the binutils issue. > > > > Link: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > Link: https://github.com/ClangBuiltLinux/linux/issues/1719 > > Signed-off-by: Nathan Chancellor <nathan@kernel.org> > > Thanks for keeping these LLVM_IAS=0 builds alive a little longer. My > hope is the GNU binutils can relax their requirement for debug info > sections to improve support for DWARF v5. > > Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> Applied to linux-kbuild. Thanks. > > --- > > > > v2: > > - Rebase on commit bb1435f3f575 ("Kconfig.debug: add toolchain > > checks for DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT") from the kbuild > > tree. > > - Limit CONFIG_AS_HAS_NON_CONST_LEB128 dependency to GNU as. There > > is no point to applying this dependency to the integrated > > assembler because it will always pass. > > - Apply the CONFIG_AS_HAS_NON_CONST_LEB128 dependency to > > CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as well, due to the > > aforementioned kbuild change. > > - Move comment block to above CONFIG_AS_HAS_NON_CONST_LEB128, as the > > configuration is now used in two places. > > - Drop Conor's tested by, as the patch is different enough to > > potentially require new testing. > > > > v1: https://lore.kernel.org/20220928182523.3105953-1-nathan@kernel.org/ > > > > lib/Kconfig.debug | 9 +++++++-- > > 1 file changed, 7 insertions(+), 2 deletions(-) > > > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > index db8d9271cabf..5c1c63575895 100644 > > --- a/lib/Kconfig.debug > > +++ b/lib/Kconfig.debug > > @@ -231,6 +231,11 @@ config DEBUG_INFO > > in the "Debug information" choice below, indicating that debug > > information will be generated for build targets. > > > > +# Clang is known to generate .{s,u}leb128 with symbol deltas with DWARF5, which > > +# some targets may not support: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > +config AS_HAS_NON_CONST_LEB128 > > + def_bool $(as-instr,.uleb128 .Lexpr_end4 - .Lexpr_start3\n.Lexpr_start3:\n.Lexpr_end4:) > > + > > choice > > prompt "Debug information" > > depends on DEBUG_KERNEL > > @@ -253,7 +258,7 @@ config DEBUG_INFO_NONE > > config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT > > bool "Rely on the toolchain's implicit default DWARF version" > > select DEBUG_INFO > > - depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502) > > + depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > help > > The implicit default version of DWARF debug info produced by a > > toolchain changes over time. > > @@ -277,7 +282,7 @@ config DEBUG_INFO_DWARF4 > > config DEBUG_INFO_DWARF5 > > bool "Generate DWARF Version 5 debuginfo" > > select DEBUG_INFO > > - depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502) > > + depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > help > > Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc > > 5.0+ accepts the -gdwarf-5 flag but only had partial support for some > > > > base-commit: bb1435f3f575b5213eaf27434efa3971f51c01de > > -- > > 2.38.0 > > > > > -- > Thanks, > ~Nick Desaulniers -- Best Regards Masahiro Yamada
On Sun, Oct 16, 2022 at 8:04 PM Masahiro Yamada <masahiroy@kernel.org> wrote: > > On Sat, Oct 15, 2022 at 6:52 AM Nick Desaulniers > <ndesaulniers@google.com> wrote: > > > > On Fri, Oct 14, 2022 at 1:48 PM Nathan Chancellor <nathan@kernel.org> wrote: > > > > > > When building with a RISC-V kernel with DWARF5 debug info using clang > > > and the GNU assembler, several instances of the following error appear: > > > > > > /tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported > > > > > > Dumping the .s file reveals these .uleb128 directives come from > > > .debug_loc and .debug_ranges: > > > > > > .Ldebug_loc0: > > > .byte 4 # DW_LLE_offset_pair > > > .uleb128 .Lfunc_begin0-.Lfunc_begin0 # starting offset > > > .uleb128 .Ltmp1-.Lfunc_begin0 # ending offset > > > .byte 1 # Loc expr size > > > .byte 90 # DW_OP_reg10 > > > .byte 0 # DW_LLE_end_of_list > > > > > > .Ldebug_ranges0: > > > .byte 4 # DW_RLE_offset_pair > > > .uleb128 .Ltmp6-.Lfunc_begin0 # starting offset > > > .uleb128 .Ltmp27-.Lfunc_begin0 # ending offset > > > .byte 4 # DW_RLE_offset_pair > > > .uleb128 .Ltmp28-.Lfunc_begin0 # starting offset > > > .uleb128 .Ltmp30-.Lfunc_begin0 # ending offset > > > .byte 0 # DW_RLE_end_of_list > > > > > > There is an outstanding binutils issue to support a non-constant operand > > > to .sleb128 and .uleb128 in GAS for RISC-V but there does not appear to > > > be any movement on it, due to concerns over how it would work with > > > linker relaxation. > > > > > > To avoid these build errors, prevent DWARF5 from being selected when > > > using clang and an assembler that does not have support for these symbol > > > deltas, which can be easily checked in Kconfig with as-instr plus the > > > small test program from the dwz test suite from the binutils issue. > > > > > > Link: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > > Link: https://github.com/ClangBuiltLinux/linux/issues/1719 > > > Signed-off-by: Nathan Chancellor <nathan@kernel.org> > > > > Thanks for keeping these LLVM_IAS=0 builds alive a little longer. My > > hope is the GNU binutils can relax their requirement for debug info > > sections to improve support for DWARF v5. > > > > Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> > > > Applied to linux-kbuild. > Thanks. > [1] says: "This looks good to me! Feel free to submit with a: Tested-by: Conor Dooley <conor.dooley@microchip.com>" -sed@- [1] https://github.com/ClangBuiltLinux/linux/issues/1719#issuecomment-1261158627 > > > > > --- > > > > > > v2: > > > - Rebase on commit bb1435f3f575 ("Kconfig.debug: add toolchain > > > checks for DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT") from the kbuild > > > tree. > > > - Limit CONFIG_AS_HAS_NON_CONST_LEB128 dependency to GNU as. There > > > is no point to applying this dependency to the integrated > > > assembler because it will always pass. > > > - Apply the CONFIG_AS_HAS_NON_CONST_LEB128 dependency to > > > CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as well, due to the > > > aforementioned kbuild change. > > > - Move comment block to above CONFIG_AS_HAS_NON_CONST_LEB128, as the > > > configuration is now used in two places. > > > - Drop Conor's tested by, as the patch is different enough to > > > potentially require new testing. > > > > > > v1: https://lore.kernel.org/20220928182523.3105953-1-nathan@kernel.org/ > > > > > > lib/Kconfig.debug | 9 +++++++-- > > > 1 file changed, 7 insertions(+), 2 deletions(-) > > > > > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > > index db8d9271cabf..5c1c63575895 100644 > > > --- a/lib/Kconfig.debug > > > +++ b/lib/Kconfig.debug > > > @@ -231,6 +231,11 @@ config DEBUG_INFO > > > in the "Debug information" choice below, indicating that debug > > > information will be generated for build targets. > > > > > > +# Clang is known to generate .{s,u}leb128 with symbol deltas with DWARF5, which > > > +# some targets may not support: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > > +config AS_HAS_NON_CONST_LEB128 > > > + def_bool $(as-instr,.uleb128 .Lexpr_end4 - .Lexpr_start3\n.Lexpr_start3:\n.Lexpr_end4:) > > > + > > > choice > > > prompt "Debug information" > > > depends on DEBUG_KERNEL > > > @@ -253,7 +258,7 @@ config DEBUG_INFO_NONE > > > config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT > > > bool "Rely on the toolchain's implicit default DWARF version" > > > select DEBUG_INFO > > > - depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502) > > > + depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > > help > > > The implicit default version of DWARF debug info produced by a > > > toolchain changes over time. > > > @@ -277,7 +282,7 @@ config DEBUG_INFO_DWARF4 > > > config DEBUG_INFO_DWARF5 > > > bool "Generate DWARF Version 5 debuginfo" > > > select DEBUG_INFO > > > - depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502) > > > + depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > > help > > > Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc > > > 5.0+ accepts the -gdwarf-5 flag but only had partial support for some > > > > > > base-commit: bb1435f3f575b5213eaf27434efa3971f51c01de > > > -- > > > 2.38.0 > > > > > > > > > -- > > Thanks, > > ~Nick Desaulniers > > > > -- > Best Regards > Masahiro Yamada
On Sun, Oct 16, 2022 at 08:10:30PM +0200, Sedat Dilek wrote: > On Sun, Oct 16, 2022 at 8:04 PM Masahiro Yamada <masahiroy@kernel.org> wrote: > > > > On Sat, Oct 15, 2022 at 6:52 AM Nick Desaulniers > > <ndesaulniers@google.com> wrote: > > > > > > On Fri, Oct 14, 2022 at 1:48 PM Nathan Chancellor <nathan@kernel.org> wrote: > > > > > > > > When building with a RISC-V kernel with DWARF5 debug info using clang > > > > and the GNU assembler, several instances of the following error appear: > > > > > > > > /tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported > > > > > > > > Dumping the .s file reveals these .uleb128 directives come from > > > > .debug_loc and .debug_ranges: > > > > > > > > .Ldebug_loc0: > > > > .byte 4 # DW_LLE_offset_pair > > > > .uleb128 .Lfunc_begin0-.Lfunc_begin0 # starting offset > > > > .uleb128 .Ltmp1-.Lfunc_begin0 # ending offset > > > > .byte 1 # Loc expr size > > > > .byte 90 # DW_OP_reg10 > > > > .byte 0 # DW_LLE_end_of_list > > > > > > > > .Ldebug_ranges0: > > > > .byte 4 # DW_RLE_offset_pair > > > > .uleb128 .Ltmp6-.Lfunc_begin0 # starting offset > > > > .uleb128 .Ltmp27-.Lfunc_begin0 # ending offset > > > > .byte 4 # DW_RLE_offset_pair > > > > .uleb128 .Ltmp28-.Lfunc_begin0 # starting offset > > > > .uleb128 .Ltmp30-.Lfunc_begin0 # ending offset > > > > .byte 0 # DW_RLE_end_of_list > > > > > > > > There is an outstanding binutils issue to support a non-constant operand > > > > to .sleb128 and .uleb128 in GAS for RISC-V but there does not appear to > > > > be any movement on it, due to concerns over how it would work with > > > > linker relaxation. > > > > > > > > To avoid these build errors, prevent DWARF5 from being selected when > > > > using clang and an assembler that does not have support for these symbol > > > > deltas, which can be easily checked in Kconfig with as-instr plus the > > > > small test program from the dwz test suite from the binutils issue. > > > > > > > > Link: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > > > Link: https://github.com/ClangBuiltLinux/linux/issues/1719 > > > > Signed-off-by: Nathan Chancellor <nathan@kernel.org> > > > > > > Thanks for keeping these LLVM_IAS=0 builds alive a little longer. My > > > hope is the GNU binutils can relax their requirement for debug info > > > sections to improve support for DWARF v5. > > > > > > Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> > > > > > > Applied to linux-kbuild. > > Thanks. > > > > [1] says: > > "This looks good to me! Feel free to submit with a: > Tested-by: Conor Dooley <conor.dooley@microchip.com>" Hey Sedat, I actually didn't take a proper look at the v2 at all... I didn't realise that Nathan dropped by T-b for v2 since he'd changed the patch enough to feel that he should. I'm not too worried about the removed T-b (espcially since Linus has just merged Masahiro's PR containing this change). Thanks though! Conor. > > -sed@- > > [1] https://github.com/ClangBuiltLinux/linux/issues/1719#issuecomment-1261158627 > > > > > > > > > --- > > > > > > > > v2: > > > > - Rebase on commit bb1435f3f575 ("Kconfig.debug: add toolchain > > > > checks for DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT") from the kbuild > > > > tree. > > > > - Limit CONFIG_AS_HAS_NON_CONST_LEB128 dependency to GNU as. There > > > > is no point to applying this dependency to the integrated > > > > assembler because it will always pass. > > > > - Apply the CONFIG_AS_HAS_NON_CONST_LEB128 dependency to > > > > CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as well, due to the > > > > aforementioned kbuild change. > > > > - Move comment block to above CONFIG_AS_HAS_NON_CONST_LEB128, as the > > > > configuration is now used in two places. > > > > - Drop Conor's tested by, as the patch is different enough to > > > > potentially require new testing. > > > > > > > > v1: https://lore.kernel.org/20220928182523.3105953-1-nathan@kernel.org/ > > > > > > > > lib/Kconfig.debug | 9 +++++++-- > > > > 1 file changed, 7 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > > > index db8d9271cabf..5c1c63575895 100644 > > > > --- a/lib/Kconfig.debug > > > > +++ b/lib/Kconfig.debug > > > > @@ -231,6 +231,11 @@ config DEBUG_INFO > > > > in the "Debug information" choice below, indicating that debug > > > > information will be generated for build targets. > > > > > > > > +# Clang is known to generate .{s,u}leb128 with symbol deltas with DWARF5, which > > > > +# some targets may not support: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > > > +config AS_HAS_NON_CONST_LEB128 > > > > + def_bool $(as-instr,.uleb128 .Lexpr_end4 - .Lexpr_start3\n.Lexpr_start3:\n.Lexpr_end4:) > > > > + > > > > choice > > > > prompt "Debug information" > > > > depends on DEBUG_KERNEL > > > > @@ -253,7 +258,7 @@ config DEBUG_INFO_NONE > > > > config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT > > > > bool "Rely on the toolchain's implicit default DWARF version" > > > > select DEBUG_INFO > > > > - depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502) > > > > + depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > > > help > > > > The implicit default version of DWARF debug info produced by a > > > > toolchain changes over time. > > > > @@ -277,7 +282,7 @@ config DEBUG_INFO_DWARF4 > > > > config DEBUG_INFO_DWARF5 > > > > bool "Generate DWARF Version 5 debuginfo" > > > > select DEBUG_INFO > > > > - depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502) > > > > + depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > > > help > > > > Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc > > > > 5.0+ accepts the -gdwarf-5 flag but only had partial support for some > > > > > > > > base-commit: bb1435f3f575b5213eaf27434efa3971f51c01de > > > > -- > > > > 2.38.0 > > > > > > > > > > > > > -- > > > Thanks, > > > ~Nick Desaulniers > > > > > > > > -- > > Best Regards > > Masahiro Yamada
On Sun, Oct 16, 2022 at 8:20 PM Conor Dooley <conor@kernel.org> wrote: > > On Sun, Oct 16, 2022 at 08:10:30PM +0200, Sedat Dilek wrote: > > On Sun, Oct 16, 2022 at 8:04 PM Masahiro Yamada <masahiroy@kernel.org> wrote: > > > > > > On Sat, Oct 15, 2022 at 6:52 AM Nick Desaulniers > > > <ndesaulniers@google.com> wrote: > > > > > > > > On Fri, Oct 14, 2022 at 1:48 PM Nathan Chancellor <nathan@kernel.org> wrote: > > > > > > > > > > When building with a RISC-V kernel with DWARF5 debug info using clang > > > > > and the GNU assembler, several instances of the following error appear: > > > > > > > > > > /tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported > > > > > > > > > > Dumping the .s file reveals these .uleb128 directives come from > > > > > .debug_loc and .debug_ranges: > > > > > > > > > > .Ldebug_loc0: > > > > > .byte 4 # DW_LLE_offset_pair > > > > > .uleb128 .Lfunc_begin0-.Lfunc_begin0 # starting offset > > > > > .uleb128 .Ltmp1-.Lfunc_begin0 # ending offset > > > > > .byte 1 # Loc expr size > > > > > .byte 90 # DW_OP_reg10 > > > > > .byte 0 # DW_LLE_end_of_list > > > > > > > > > > .Ldebug_ranges0: > > > > > .byte 4 # DW_RLE_offset_pair > > > > > .uleb128 .Ltmp6-.Lfunc_begin0 # starting offset > > > > > .uleb128 .Ltmp27-.Lfunc_begin0 # ending offset > > > > > .byte 4 # DW_RLE_offset_pair > > > > > .uleb128 .Ltmp28-.Lfunc_begin0 # starting offset > > > > > .uleb128 .Ltmp30-.Lfunc_begin0 # ending offset > > > > > .byte 0 # DW_RLE_end_of_list > > > > > > > > > > There is an outstanding binutils issue to support a non-constant operand > > > > > to .sleb128 and .uleb128 in GAS for RISC-V but there does not appear to > > > > > be any movement on it, due to concerns over how it would work with > > > > > linker relaxation. > > > > > > > > > > To avoid these build errors, prevent DWARF5 from being selected when > > > > > using clang and an assembler that does not have support for these symbol > > > > > deltas, which can be easily checked in Kconfig with as-instr plus the > > > > > small test program from the dwz test suite from the binutils issue. > > > > > > > > > > Link: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > > > > Link: https://github.com/ClangBuiltLinux/linux/issues/1719 > > > > > Signed-off-by: Nathan Chancellor <nathan@kernel.org> > > > > > > > > Thanks for keeping these LLVM_IAS=0 builds alive a little longer. My > > > > hope is the GNU binutils can relax their requirement for debug info > > > > sections to improve support for DWARF v5. > > > > > > > > Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> > > > > > > > > > Applied to linux-kbuild. > > > Thanks. > > > > > > > [1] says: > > > > "This looks good to me! Feel free to submit with a: > > Tested-by: Conor Dooley <conor.dooley@microchip.com>" > > Hey Sedat, > > I actually didn't take a proper look at the v2 at all... I didn't realise > that Nathan dropped by T-b for v2 since he'd changed the patch enough to > feel that he should. > > I'm not too worried about the removed T-b (espcially since Linus has > just merged Masahiro's PR containing this change). > > Thanks though! > Conor. > Yes, just saw the update on https://github.com/torvalds/linux/commits/master first. -Sedat- > > > > -sed@- > > > > [1] https://github.com/ClangBuiltLinux/linux/issues/1719#issuecomment-1261158627 > > > > > > > > > > > > > --- > > > > > > > > > > v2: > > > > > - Rebase on commit bb1435f3f575 ("Kconfig.debug: add toolchain > > > > > checks for DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT") from the kbuild > > > > > tree. > > > > > - Limit CONFIG_AS_HAS_NON_CONST_LEB128 dependency to GNU as. There > > > > > is no point to applying this dependency to the integrated > > > > > assembler because it will always pass. > > > > > - Apply the CONFIG_AS_HAS_NON_CONST_LEB128 dependency to > > > > > CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT as well, due to the > > > > > aforementioned kbuild change. > > > > > - Move comment block to above CONFIG_AS_HAS_NON_CONST_LEB128, as the > > > > > configuration is now used in two places. > > > > > - Drop Conor's tested by, as the patch is different enough to > > > > > potentially require new testing. > > > > > > > > > > v1: https://lore.kernel.org/20220928182523.3105953-1-nathan@kernel.org/ > > > > > > > > > > lib/Kconfig.debug | 9 +++++++-- > > > > > 1 file changed, 7 insertions(+), 2 deletions(-) > > > > > > > > > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > > > > index db8d9271cabf..5c1c63575895 100644 > > > > > --- a/lib/Kconfig.debug > > > > > +++ b/lib/Kconfig.debug > > > > > @@ -231,6 +231,11 @@ config DEBUG_INFO > > > > > in the "Debug information" choice below, indicating that debug > > > > > information will be generated for build targets. > > > > > > > > > > +# Clang is known to generate .{s,u}leb128 with symbol deltas with DWARF5, which > > > > > +# some targets may not support: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 > > > > > +config AS_HAS_NON_CONST_LEB128 > > > > > + def_bool $(as-instr,.uleb128 .Lexpr_end4 - .Lexpr_start3\n.Lexpr_start3:\n.Lexpr_end4:) > > > > > + > > > > > choice > > > > > prompt "Debug information" > > > > > depends on DEBUG_KERNEL > > > > > @@ -253,7 +258,7 @@ config DEBUG_INFO_NONE > > > > > config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT > > > > > bool "Rely on the toolchain's implicit default DWARF version" > > > > > select DEBUG_INFO > > > > > - depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502) > > > > > + depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > > > > help > > > > > The implicit default version of DWARF debug info produced by a > > > > > toolchain changes over time. > > > > > @@ -277,7 +282,7 @@ config DEBUG_INFO_DWARF4 > > > > > config DEBUG_INFO_DWARF5 > > > > > bool "Generate DWARF Version 5 debuginfo" > > > > > select DEBUG_INFO > > > > > - depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502) > > > > > + depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) > > > > > help > > > > > Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc > > > > > 5.0+ accepts the -gdwarf-5 flag but only had partial support for some > > > > > > > > > > base-commit: bb1435f3f575b5213eaf27434efa3971f51c01de > > > > > -- > > > > > 2.38.0 > > > > > > > > > > > > > > > > > -- > > > > Thanks, > > > > ~Nick Desaulniers > > > > > > > > > > > > -- > > > Best Regards > > > Masahiro Yamada
On Fri, 14 Oct 2022 13:42:11 -0700 Nathan Chancellor <nathan@kernel.org> wrote: > When building with a RISC-V kernel with DWARF5 debug info using clang > and the GNU assembler, several instances of the following error appear: > > /tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported hm, which kernels want this? I could merge it for 6.1, which seems suitable. If we want it backported into earlier kernels then a Fixes: would be nice, to prevent it from being ported back further than necessary.
Hi Andrew, On Sun, Oct 16, 2022 at 05:28:15PM -0700, Andrew Morton wrote: > On Fri, 14 Oct 2022 13:42:11 -0700 Nathan Chancellor <nathan@kernel.org> wrote: > > > When building with a RISC-V kernel with DWARF5 debug info using clang > > and the GNU assembler, several instances of the following error appear: > > > > /tmp/vgettimeofday-48aa35.s:2963: Error: non-constant .uleb128 is not supported > > hm, which kernels want this? > > I could merge it for 6.1, which seems suitable. If we want it > backported into earlier kernels then a Fixes: would be nice, to prevent > it from being ported back further than necessary. Masahiro took this for 6.1 via the kbuild tree, it is now in mainline as commit 0a6de78cff60 ("lib/Kconfig.debug: Add check for non-constant .{s,u}leb128 support to DWARF5"). It does need to go to stable but it needs a few prerequisite changes to cover all cases and I did not want to try and describe those dependencies in the patch itself. I should be able to handle the backports manually tomorrow. Cheers, Nathan
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index db8d9271cabf..5c1c63575895 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -231,6 +231,11 @@ config DEBUG_INFO in the "Debug information" choice below, indicating that debug information will be generated for build targets. +# Clang is known to generate .{s,u}leb128 with symbol deltas with DWARF5, which +# some targets may not support: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 +config AS_HAS_NON_CONST_LEB128 + def_bool $(as-instr,.uleb128 .Lexpr_end4 - .Lexpr_start3\n.Lexpr_start3:\n.Lexpr_end4:) + choice prompt "Debug information" depends on DEBUG_KERNEL @@ -253,7 +258,7 @@ config DEBUG_INFO_NONE config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT bool "Rely on the toolchain's implicit default DWARF version" select DEBUG_INFO - depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502) + depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) help The implicit default version of DWARF debug info produced by a toolchain changes over time. @@ -277,7 +282,7 @@ config DEBUG_INFO_DWARF4 config DEBUG_INFO_DWARF5 bool "Generate DWARF Version 5 debuginfo" select DEBUG_INFO - depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502) + depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) help Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc 5.0+ accepts the -gdwarf-5 flag but only had partial support for some