From: Jim Wilson <jimw@sifive.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
James Clarke <jrtc27@jrtc27.com>,
Andrew Waterman <andrew@sifive.com>,
Kito Cheng <kito.cheng@sifive.com>
Subject: Re: [PATCH] riscv: Resolve symbols directly for symbols with STO_RISCV_VARIANT_CC.
Date: Mon, 25 Oct 2021 14:08:26 -0700 [thread overview]
Message-ID: <CAFyWVaaUBy6-vL-gZvsSqWiAqOcRoiVZ5_Dn4yFceYw4BMHjyA@mail.gmail.com> (raw)
In-Reply-To: <mhng-ead6bb12-f7cb-4d09-8dd8-8c828efe0e14@palmerdabbelt-glaptop>
On Wed, Aug 11, 2021 at 4:52 PM Palmer Dabbelt <palmer@dabbelt.com> wrote:
> IIUC the ABI patch still isn't merged, which is what makes it actually
> official. I'll take this when it lands.
>
Just following up, the psABI patch was merged in
https://github.com/riscv/riscv-elf-psabi-doc/pull/190
and the psABI has gone into public review for the first official release.
So we would like this patch from Kai merged in.
https://sourceware.org/pipermail/libc-alpha/2021-August/129931.html
in case you lost track of the original message on this thread.
Jim
next prev parent reply other threads:[~2021-10-25 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 3:47 [PATCH] riscv: Resolve symbols directly for symbols with STO_RISCV_VARIANT_CC Hsiangkai Wang
2021-08-11 22:11 ` Palmer Dabbelt
2021-08-11 22:51 ` Jessica Clarke
2021-08-11 23:00 ` Jim Wilson
2021-08-11 23:21 ` Palmer Dabbelt
2021-08-11 23:32 ` Jessica Clarke
2021-08-11 23:52 ` Palmer Dabbelt
2021-08-12 0:54 ` Jessica Clarke
2021-10-25 21:08 ` Jim Wilson [this message]
2021-12-02 20:21 ` Palmer Dabbelt
2021-12-02 21:06 ` Jessica Clarke
2021-12-02 21:09 ` Andrew Waterman
2021-12-02 21:44 ` Florian Weimer via Libc-alpha
2021-12-02 22:08 ` Jessica Clarke
2021-10-29 0:20 ` DJ Delorie via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyWVaaUBy6-vL-gZvsSqWiAqOcRoiVZ5_Dn4yFceYw4BMHjyA@mail.gmail.com \
--to=jimw@sifive.com \
--cc=andrew@sifive.com \
--cc=jrtc27@jrtc27.com \
--cc=kito.cheng@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@dabbelt.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).