From: Nelson Chu <nelson@rivosinc.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: binutils@sourceware.org, nelson.rivosinc.com@nelsondembp.localdomain
Subject: Re: [PATCH] RISC-V: Removed privileged spec 1.9.1 support in assembler.
Date: Thu, 28 Mar 2024 10:23:35 +0800 [thread overview]
Message-ID: <CAPpQWtCEwCgr-VvN+nAY-S4s+9u=ea1PiXhK-y=DZhm6-pVBHQ@mail.gmail.com> (raw)
In-Reply-To: <CA+yXCZCH7CZar52XM19SVHi=b46EEg48jqSbtqSOsJ7GbqGBSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
Thanks, committed.
Nelson
On Mon, Mar 25, 2024 at 9:58 PM Kito Cheng <kito.cheng@gmail.com> wrote:
> > Removed since it's may have lots of conflicts with the newer extensions,
> but
> > still keep linker recognizes it in case of linking old objects.
>
> LGTM, and hope one day we can get rid of whole -mpriv-spec= option :P
>
prev parent reply other threads:[~2024-03-28 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 8:14 Nelson Chu
2024-03-25 13:58 ` Kito Cheng
2024-03-28 2:23 ` Nelson Chu [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='CAPpQWtCEwCgr-VvN+nAY-S4s+9u=ea1PiXhK-y=DZhm6-pVBHQ@mail.gmail.com' \
--to=nelson@rivosinc.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@gmail.com \
--cc=nelson.rivosinc.com@nelsondembp.localdomain \
/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).