From: Kito Cheng <kito.cheng@sifive.com>
To: Vineet Gupta <vineetg@rivosinc.com>
Cc: "Vincent Chen" <vincent.chen@sifive.com>,
libc-alpha@sourceware.org, palmer@dabbelt.com,
darius@bluespec.com, andrew@sifive.com, dj@redhat.com,
greentime.hu@sifive.com, "Andy Chiu" <andy.chiu@sifive.com>,
"Björn Töpel" <bjorn@kernel.org>,
davidlt@rivosinc.com, "Arnd Bergmann" <arnd@kernel.org>,
"Florian Weimer" <fweimer@redhat.com>,
"Nelson Chu" <nelson@rivosinc.com>
Subject: Re: [PATCH v2 2/2] riscv: Resolve symbols directly for symbols with STO_RISCV_VARIANT_CC.
Date: Fri, 9 Dec 2022 12:35:18 +0800 [thread overview]
Message-ID: <CALLt3Tj8N8zyvi5exUTO17kRRoC3Ja-9usduDZSb3Wk+02FjnA@mail.gmail.com> (raw)
In-Reply-To: <eb89fdac-03cd-f80a-87e6-de72bed5d9b6@rivosinc.com>
> Not sure what you mean. Are you saying that even though the current ABI
> doesn't require it, we should still add it to glibc, won't it bitrot.
> I don't feel strongly either ways, but IMO this should be done when the
> ABI is actually changed.
STO_RISCV_VARIANT_CC has already been defined and released in psABI 1.0,
and this patch is implementing a feature in released psABI,
so I think this is fine to upstream from psABI perspective.
prev parent reply other threads:[~2022-12-09 4:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 4:31 [PATCH v2 0/2] RISC-V: Add vector ISA support Vincent Chen
2022-01-18 4:31 ` [PATCH v2 1/2] RISC-V: remove riscv-specific sigcontext.h Vincent Chen
2022-01-20 2:36 ` Palmer Dabbelt
2022-01-20 2:47 ` Kito Cheng
2022-01-21 1:29 ` Vincent Chen
2022-01-24 9:42 ` Vincent Chen
2022-02-24 20:56 ` Palmer Dabbelt
2022-02-25 0:32 ` Vincent Chen
2022-01-18 4:31 ` [PATCH v2 2/2] riscv: Resolve symbols directly for symbols with STO_RISCV_VARIANT_CC Vincent Chen
2022-01-20 2:21 ` Palmer Dabbelt
2022-01-20 2:38 ` H.J. Lu
2022-01-20 2:43 ` Palmer Dabbelt
2022-01-21 1:43 ` Vincent Chen
2022-02-24 20:56 ` Palmer Dabbelt
2022-12-09 4:11 ` Vineet Gupta
2022-12-09 4:22 ` Kito Cheng
2022-12-09 4:26 ` Vineet Gupta
2022-12-09 4:35 ` Kito Cheng [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=CALLt3Tj8N8zyvi5exUTO17kRRoC3Ja-9usduDZSb3Wk+02FjnA@mail.gmail.com \
--to=kito.cheng@sifive.com \
--cc=andrew@sifive.com \
--cc=andy.chiu@sifive.com \
--cc=arnd@kernel.org \
--cc=bjorn@kernel.org \
--cc=darius@bluespec.com \
--cc=davidlt@rivosinc.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=greentime.hu@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=vincent.chen@sifive.com \
--cc=vineetg@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 read-only IMAP folder(s) and NNTP newsgroup(s).