linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nick Clifton <nickc@redhat.com>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <natechancellor@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Clang-Built-Linux ML <clang-built-linux@googlegroups.com>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	Fangrui Song <maskray@google.com>,
	Caroline Tice <cmtice@google.com>, Yonghong Song <yhs@fb.com>,
	Jiri Olsa <jolsa@kernel.org>, Andrii Nakryiko <andrii@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Arvind Sankar <nivedita@alum.mit.edu>
Subject: Re: [PATCH v6 2/2] Kbuild: implement support for DWARF v5
Date: Fri, 29 Jan 2021 23:09:39 +0100	[thread overview]
Message-ID: <20210129220939.GY4020736@tucnak> (raw)
In-Reply-To: <CAKwvOdm-+xK=diSKKXXnS2m1+W6QZ70c7cRKTbtVF=dWi1_8_w@mail.gmail.com>

On Fri, Jan 29, 2021 at 02:05:59PM -0800, Nick Desaulniers wrote:
> Ah, I see.  Then I should update the script I add
> (scripts/test_dwarf5_support.sh) to feature detect that bug, since
> it's the latest of the bunch.  Also, should update my comment to note
> that this requires binutils greater than 2.35.1 (which is what I have,
> which fails, since the backport landed in ... what?!)  How was this
> backported to 2.35
> (https://sourceware.org/bugzilla/show_bug.cgi?id=27195#c12, Jan 26
> 2021) when binutils-2_35_1 was tagged sept 19 2020?  Or will there be
> a binutils 2.35.2 point release?

AFAIK yes, soon.

	Jakub


  reply	other threads:[~2021-01-29 22:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 19:43 [PATCH v6 0/2] Kbuild: DWARF v5 support Nick Desaulniers
2021-01-29 19:43 ` [PATCH v6 1/2] Kbuild: make DWARF version a choice Nick Desaulniers
2021-01-29 20:17   ` Jakub Jelinek
2021-01-29 20:19     ` Nick Desaulniers
2021-01-29 20:57       ` Nick Desaulniers
2021-01-29 21:32         ` Arvind Sankar
2021-01-29 21:41           ` Jakub Jelinek
2021-01-29 22:40             ` Nick Desaulniers
2021-01-29 19:43 ` [PATCH v6 2/2] Kbuild: implement support for DWARF v5 Nick Desaulniers
2021-01-29 20:41   ` Sedat Dilek
2021-01-29 20:48     ` Nick Desaulniers
2021-01-29 20:54       ` Sedat Dilek
2021-01-29 21:09         ` Nick Desaulniers
2021-01-29 21:13           ` Sedat Dilek
2021-01-29 21:20             ` Sedat Dilek
2021-01-29 22:09               ` Nick Desaulniers
2021-01-29 22:11                 ` Sedat Dilek
2021-01-29 22:20                   ` Nick Desaulniers
2021-01-29 22:23                     ` Sedat Dilek
2021-01-29 22:31                       ` Nick Desaulniers
2021-01-29 22:42                         ` Sedat Dilek
2021-02-03  7:56                           ` Masahiro Yamada
2021-01-29 20:57       ` Jakub Jelinek
2021-01-29 21:05         ` Nick Desaulniers
2021-01-29 21:11           ` Jakub Jelinek
2021-01-29 22:05             ` Nick Desaulniers
2021-01-29 22:09               ` Jakub Jelinek [this message]
2021-01-29 23:25                 ` Nick Desaulniers
2021-01-29 23:30                   ` Nick Desaulniers
2021-01-29 22:27             ` Nick Desaulniers
2021-01-29 21:51   ` Fangrui Song
2021-01-29 22:07     ` Nick Desaulniers
2021-01-29 22:47   ` Fangrui Song
2021-01-29 20:03 ` [PATCH v6 0/2] Kbuild: DWARF v5 support Sedat Dilek
2021-01-30  0:08 ` Sedat Dilek
2021-01-30  0:46   ` Nick Desaulniers
2021-01-30  0:58     ` Fāng-ruì Sòng

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=20210129220939.GY4020736@tucnak \
    --to=jakub@redhat.com \
    --cc=acme@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=cmtice@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=maskray@google.com \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=nickc@redhat.com \
    --cc=nivedita@alum.mit.edu \
    --cc=sedat.dilek@gmail.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).