mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	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
Subject: Re: [PATCH v2] lib/Kconfig.debug: Add check for non-constant .{s,u}leb128 support to DWARF5
Date: Sun, 16 Oct 2022 17:28:15 -0700	[thread overview]
Message-ID: <20221016172815.f5a5f1f86af7ff1937a2e273@linux-foundation.org> (raw)
In-Reply-To: <20221014204210.383380-1-nathan@kernel.org>

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.


  parent reply	other threads:[~2022-10-17  0:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 20:42 Nathan Chancellor
2022-10-14 21:51 ` Nick Desaulniers
2022-10-16 18:00   ` Masahiro Yamada
2022-10-16 18:10     ` Sedat Dilek
2022-10-16 18:20       ` Conor Dooley
2022-10-16 18:22         ` Sedat Dilek
2022-10-17  0:28 ` Andrew Morton [this message]
2022-10-17  0:41   ` Nathan Chancellor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221016172815.f5a5f1f86af7ff1937a2e273@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=conor@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=palmer@dabbelt.com \
    --cc=patches@lists.linux.dev \
    --cc=trix@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®