From: Nathan Chancellor <nathan@kernel.org>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, macro@orcam.me.uk
Subject: Re: [PATCH v3] riscv: asm: use .insn for making custom instructions
Date: Fri, 31 Oct 2025 16:27:11 -0400 [thread overview]
Message-ID: <20251031202711.GC2486902@ax162> (raw)
In-Reply-To: <20251031-980f37fdcb94d15b02945fce@orel>
On Fri, Oct 31, 2025 at 02:08:33PM -0500, Andrew Jones wrote:
> Or we can change the test in 'config AS_HAS_INSN' to use the hex encoded
> input. We'd completely stop using .insn for LLVM older than 19 and GNU
> binutils older than 2.38, but that's probably better than adding yet
> another config.
Yeah, that would obviously work too. I was not sure how tolerable it was
to lose the use of .insn altogether for those versions hence the split
suggestion but if it is not that big of a deal, might as well check for
the extended .insn upfront.
Cheers,
Nathan
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-10-31 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 17:16 [PATCH v3] riscv: asm: use .insn for making custom instructions Ben Dooks
2025-10-28 1:10 ` patchwork-bot+linux-riscv
2025-10-31 3:10 ` Nathan Chancellor
2025-10-31 19:08 ` Andrew Jones
2025-10-31 20:27 ` Nathan Chancellor [this message]
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=20251031202711.GC2486902@ax162 \
--to=nathan@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-riscv@lists.infradead.org \
--cc=macro@orcam.me.uk \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.