linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: luc.vanoostenryck@gmail.com, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] RISC-V: Add support fo the zihintpause extension
Date: Fri, 15 Dec 2023 13:41:55 +0100 (CET)	[thread overview]
Message-ID: <b26c790-c192-8b70-9947-cb6ff6a9ac55@linux-m68k.org> (raw)
In-Reply-To: <20220811053356.17375-1-palmer@rivosinc.com>

On Wed, 10 Aug 2022, Palmer Dabbelt wrote:
> This was recently added to binutils and with any luck will soon be in
> Linux, without it sparse will fail when trying to build new kernels on
> systems with new toolchains.
>
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

As I've just run into

     .../linux$ make C=1

     [...]

     invalid argument to '-march': '_zicsr_zifencei_zihintpause'

and needed to apply this patch before upgrading sparse:

Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

 						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
 							    -- Linus Torvalds

  parent reply	other threads:[~2023-12-15 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  5:33 [PATCH] RISC-V: Add support fo the zihintpause extension Palmer Dabbelt
2022-08-12  8:33 ` Conor Dooley
2023-12-15 12:41 ` Geert Uytterhoeven [this message]
2023-12-18 13:59 ` Luc Van Oostenryck
  -- strict thread matches above, loose matches on Subject: below --
2022-08-11  5:29 Palmer Dabbelt

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=b26c790-c192-8b70-9947-cb6ff6a9ac55@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=palmer@rivosinc.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).