From: Nick Clifton <nickc@redhat.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH 1/4] opcodes: use CGEN_INSN_LGUINT for base instructions
Date: Wed, 17 May 2023 14:03:58 +0100 [thread overview]
Message-ID: <a584613a-5dff-dfaf-be55-90e73d99e791@redhat.com> (raw)
In-Reply-To: <20230511141351.18886-2-jose.marchesi@oracle.com>
Hi Jose,
> This patch changes the opcodes CGEN support code in order to allow
> base instructions with opcodes past the least significative 32 bits.
>
> Note that the masks have been adapted in a previous patch.
>
> This patch has been regtested for all the current targets in binutils
> that are based on CGEN, namely:
>
> - bpf-unknown-none
> - lm32-elf
> - fr30-elf
> - ip2k-elf
> - iq2000-elf
> - m32c-elf
> - m32r-elf
> - mep-elf
> - mt-elf
> - or1k-elf
> - stormy16-elf"
>
> Also with --enable-cgen-maint and --enable-targets=all.
> No regressions observed.
Patch approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2023-05-17 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 14:13 [PATCH 0/4] Add support for V3 BPF atomic instructions Jose E. Marchesi
2023-05-11 14:13 ` [PATCH 1/4] opcodes: use CGEN_INSN_LGUINT for base instructions Jose E. Marchesi
2023-05-11 16:05 ` Jan Beulich
2023-05-17 13:03 ` Nick Clifton [this message]
2023-05-17 14:03 ` Jose E. Marchesi
2023-07-21 22:34 ` David Faust
2023-07-22 6:53 ` Jose E. Marchesi
2023-05-11 14:13 ` [PATCH 2/4] cpu: add V3 BPF atomic instructions Jose E. Marchesi
2023-05-11 14:13 ` [PATCH 3/4] gas: add tests for BPF V3 " Jose E. Marchesi
2023-05-11 14:13 ` [PATCH 4/4] gas: document V3 BPF atomic instructions in the GAS manual Jose E. Marchesi
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=a584613a-5dff-dfaf-be55-90e73d99e791@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jose.marchesi@oracle.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 read-only IMAP folder(s) and NNTP newsgroup(s).