public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Nathan Huckleberry <nhuck@google.com>, binutils@sourceware.org
Cc: nhuck@pmull.org
Subject: Re: [PATCH 09/14] Allow nested implications for extensions.
Date: Fri, 30 Jun 2023 14:44:59 -0600	[thread overview]
Message-ID: <91af0cee-baf3-fea1-9364-db269a232051@gmail.com> (raw)
In-Reply-To: <20230629171839.573187-10-nhuck@google.com>



On 6/29/23 11:18, Nathan Huckleberry via Binutils wrote:
> Certain extensions require two levels of implications.  For example,
> zvkng implies zvkn and zvkn implies zvkned.  Enabling zvkng should also
> enable zvkned.
> 
> This patch fixes this behavior.
> 
> Signed-off-by: Nathan Huckleberry <nhuck@google.com>
> ---
>   bfd/elfxx-riscv.c | 16 ++++++++++++++--
>   1 file changed, 14 insertions(+), 2 deletions(-)
No problem with the actual code.  I would suggest a comment explicitly 
stating this only allows two levels rather than arbitrary levels of nesting.

As with the others, it needs ChangeLog and NEWS entries.

With those changes it'll be fine for the trunk.

Thanks,
jeff

  reply	other threads:[~2023-06-30 20:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 17:18 [PATCH 00/14] Support RISC-V Vector Cryptography Extensions Nathan Huckleberry
2023-06-29 17:18 ` [PATCH 01/14] Add support for the Zvbb ISA extension Nathan Huckleberry
2023-06-30 17:51   ` Jeff Law
2023-06-30 20:29     ` Christoph Müllner
2023-06-30 20:57       ` Jeff Law
2023-06-30 22:01         ` Christoph Müllner
2023-06-30 22:16           ` Palmer Dabbelt
2023-06-29 17:18 ` [PATCH 02/14] Add support for the Zvbc " Nathan Huckleberry
2023-06-30 17:56   ` Jeff Law
2023-06-29 17:18 ` [PATCH 03/14] Add support for the Zvkg " Nathan Huckleberry
2023-06-29 17:18 ` [PATCH 04/14] Add support for the Zvkned " Nathan Huckleberry
2023-06-30 19:30   ` Jeff Law
2023-06-29 17:18 ` [PATCH 05/14] Add support for the Zvknh[a,b] ISA extensions Nathan Huckleberry
2023-06-30 19:33   ` Jeff Law
2023-06-29 17:18 ` [PATCH 06/14] Add support for the Zvksed ISA extension Nathan Huckleberry
2023-06-30 20:06   ` Jeff Law
2023-06-29 17:18 ` [PATCH 07/14] Adds support for the Zvksh " Nathan Huckleberry
2023-06-30 20:08   ` Jeff Law
2023-06-29 17:18 ` [PATCH 08/14] Add support for the Zvkn " Nathan Huckleberry
2023-06-30 20:12   ` Jeff Law
2023-06-29 17:18 ` [PATCH 09/14] Allow nested implications for extensions Nathan Huckleberry
2023-06-30 20:44   ` Jeff Law [this message]
2023-06-30 21:53     ` Christoph Müllner
2023-06-30 22:24       ` Jeff Law
2023-06-30 23:48         ` Nathan Huckleberry
2023-07-01  5:22         ` Christoph Müllner
2023-07-01 13:08           ` Jeff Law
2023-07-01 13:33           ` Jeff Law
2023-07-02 20:01             ` Christoph Müllner
2023-07-05 21:29               ` Jeff Law
2023-06-29 17:18 ` [PATCH 10/14] Add support for the Zvkng ISA extension Nathan Huckleberry
2023-06-30 20:14   ` Jeff Law
2023-06-29 17:18 ` [PATCH 11/14] Add support for the Zvks " Nathan Huckleberry
2023-06-29 17:18 ` [PATCH 12/14] Add support for the Zvksg " Nathan Huckleberry
2023-06-29 17:18 ` [PATCH 13/14] Add support for the Zvknc " Nathan Huckleberry
2023-06-29 17:18 ` [PATCH 14/14] Add support for the Zvksc " Nathan Huckleberry

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=91af0cee-baf3-fea1-9364-db269a232051@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nhuck@google.com \
    --cc=nhuck@pmull.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 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).